Last verified: 2026-06-18T03:37:58Z
This page records real public interactions around oss-signal and the
boundaries for recognizing them. It is intentionally conservative: stars,
follows, reciprocal stars, and social posts are not counted as adoption.
| Interaction | Public link | How it is counted |
|---|---|---|
| Inbound external contributor PR | #14 | Merged contributor evidence from ded-furby; not independent maintainer adoption. |
| Public external fork | https://github.com/ded-furby/oss-signal | Contributor workflow evidence for PR #14; not adoption. |
| Outside-maintainer-accepted PR | icoretech/codex-action#24 | Accepted external maintainer evidence because the maintainer merged the focused docs fix. |
| Maintainer merge comment | icoretech/codex-action#24 (comment) | Public maintainer response confirming the accepted fix. |
| One-time independent-run request | icoretech/codex-action#24 (comment) | Pending request only; not adoption unless the maintainer runs, replies, or files feedback. |
| Public interest signals | 2 stars, 1 fork | Low interest signals only; not proof of quality, popularity, or adoption. |
The public stargazers page was checked on 2026-06-18 and showed one outside
stargazer, sa00441113, plus the repository owner. The public forks page
showed ded-furby/oss-signal.
No reciprocal star, follow, or promotional request is made from these signals. The only useful next step for someone who arrived through a star, fork, or profile visit is optional maintainer evidence:
- open trial feedback with a repository or workflow link
- run the no-fail workflow in a maintainer-owned public repository
- reply with a concrete reason the report is not useful
- open a focused PR only when there is a real repository-specific fix
Do not tag stargazers or fork owners just to create activity. If a fork or star turns into a public run, maintainer reply, focused PR, or trial-feedback issue, then link that new public artifact here and in the evidence ledger.
The project recognizes public work that helps maintainers evaluate or improve the tool:
- merged contributor PRs
- maintainer replies with concrete feedback
- public workflow runs in maintainer-owned repositories
- accepted external PRs informed by an
oss-signalaudit - neutral or negative trial feedback that improves the rules
Recognition means linking the public contribution in the evidence ledger, reviewer docs, ACKNOWLEDGEMENTS.md, release notes when relevant, or future thank-you comments when write access is available. For social replies, use the bounded templates in social-launch.md only when the thread is directly relevant.
oss-signal does not do star-for-star, follow-for-follow, reciprocal PRs, or
repeated comment bumps. A star can be appreciated, but it is not evidence of
adoption and should not be repaid just to influence a reviewer.
It is fine for maintainers to star repositories they independently find useful. Those stars are not tracked here as application evidence.
The strongest next interaction is still one of:
- a public workflow run in a repository not owned by
SalmonPlays - a maintainer reply on an external issue, PR, or discussion
- a public trial feedback issue with a repository or workflow link
- an additional outside-maintainer-accepted PR
Until that happens, open PRs, pending requests, stars, forks, and social posts remain supporting context only.