Use these posts to share oss-signal without overstating adoption or asking for vanity stars.
oss-signal is an OSS maintainer-readiness CLI and GitHub Action. It turns visible repository signals into Markdown, JSON, SARIF, issue-ready reports, inventory reports, PR-sized maintainer plans, and no-fail workflow trials.
Best audience:
Do not claim broad adoption. The current evidence is a public npm package, GitHub Marketplace Action, self-audit, workflow demo, no-fail maintainer trial workflow, six public field-audit issues, five open external follow-up PRs, and one merged external documentation PR.
I built oss-signal for OSS maintainers:
- CLI + GitHub Action
- Markdown / JSON / SARIF output
- issue-ready reports
- inventory mode for multiple repos
- PR-sized maintainer plans
- no-fail workflow generator
npm:
https://www.npmjs.com/package/oss-signal
Action:
https://github.com/marketplace/actions/oss-signal
Looking for maintainer feedback.
OSS maintainers: I am looking for one independent maintainer to try oss-signal in report-only mode.
It is a no-fail GitHub Action trial:
- reads repo files only
- publishes a step summary
- uploads oss-signal-report.md
- does not gate CI unless you later add fail-under
Trial:
https://github.com/SalmonPlays/oss-signal/blob/main/docs/maintainer-trial.md
Repo:
https://github.com/SalmonPlays/oss-signal
No stars or endorsements needed. A public workflow run, issue reply, or "not useful because..." note is enough feedback.
oss-signal is now on npm + GitHub Marketplace.
It audits maintainer-readiness signals and turns them into Markdown, SARIF, issue-ready reports, inventory reports, and PR-sized cleanup plans.
Repo:
https://github.com/SalmonPlays/oss-signal
`oss-signal` v0.8.4 is live on npm and GitHub Marketplace.
The tool is built for OSS maintainers and contributors who want a small, repeatable way to check maintainer-readiness signals before opening cleanup issues or PRs.
Current outputs:
- Markdown report
- JSON report
- SARIF for Code Scanning
- issue-ready Markdown
- repository inventory report
- PR-sized maintainer plan
- no-fail workflow output
Current evidence:
- npm package: https://www.npmjs.com/package/oss-signal
- GitHub Marketplace Action: https://github.com/marketplace/actions/oss-signal
- reviewer evidence: https://github.com/SalmonPlays/oss-signal/blob/main/docs/reviewer-evidence.md
- adoption evidence: https://github.com/SalmonPlays/oss-signal/blob/main/docs/adoption-evidence.md
Feedback wanted:
- Which maintainer signals are missing?
- Which reports would make cleanup PRs easier to review?
- Would you prefer Action-first, CLI-first, or issue-template-first usage?
I published oss-signal, a small OSS maintainer-readiness CLI and GitHub Action.
It checks repository signals like README, license, contributing guide, security policy, CI, tests, templates, Dependabot, CodeQL, and release notes, then produces Markdown, JSON, SARIF, issue-ready output, inventory reports, PR-sized maintainer plans, and no-fail workflow trials.
The goal is not to replace maintainer judgment. The goal is to reduce review cost and help contributors open smaller, more useful cleanup PRs.
Repo: https://github.com/SalmonPlays/oss-signal
npm: https://www.npmjs.com/package/oss-signal
Marketplace: https://github.com/marketplace/actions/oss-signal
Use only in relevant communities and only if the post fits the rules.
Show: oss-signal, a small CLI/GitHub Action for OSS maintainer-readiness audits
I built oss-signal to help maintainers and contributors turn repository hygiene checks into concrete reports and small cleanup PRs.
It checks visible maintainer signals such as README, license, contributing guide, security policy, CI, tests, issue/PR templates, Dependabot, CodeQL, and release notes.
It can output Markdown, JSON, SARIF, issue-ready Markdown, inventory reports, PR-sized maintainer plans, and no-fail workflow trials.
Repo: https://github.com/SalmonPlays/oss-signal