oss-signal v0.10.0

oss-signal v0.10.0 makes maintainer-readiness results safer to automate and
easier to compare over time.

What Changed

• Added a funding-readiness rule and expanded the catalog to 17 rules with 113
  weighted points.
• Made GitHub URL audits honor committed .oss-signal.json,
  .oss-signalrc.json, and oss-signal.config.json files at the audited ref.
• Added baseline comparison and --fail-on-regression so CI can reject newly
  broken checks without imposing an arbitrary score threshold.
• Added CI-friendly env output and complete GitHub Action outputs for check
  counts and weighted scoring totals.
• Added structured priority, impact, category, suggested-file, and verification
  metadata to recommendations.
• Tightened numeric input validation and aligned the published JSON schemas with
  every field emitted by single-repository and inventory reports.
• Hardened release, package, workflow pinning, evidence verification, and
  reviewer-readiness checks.

Upgrade Notes

The rule catalog now includes funding. Repositories without a public funding
destination can document the rule as not applicable in .oss-signal.json
instead of publishing an inactive funding link.

Existing JSON consumers should validate against the updated schemas. The
release adds fields but preserves the existing score, grade, checks, and
recommendations structure.

Try It

npm exec --yes --package=oss-signal@0.10.0 -- oss-signal . --format summary

To compare against a saved JSON report:

npm exec --yes --package=oss-signal@0.10.0 -- oss-signal . \
  --baseline previous-report.json \
  --fail-on-regression

oss-signal v0.9.9

oss-signal v0.9.9 removes the main setup hurdle for a first maintainer trial.

What Changed

• npx oss-signal --init creates a report-only workflow in the current repository.
• The generated workflow runs manually or on pull requests, uploads the Markdown
  report and adoption pack, and does not add a score gate.
• Existing workflow files are never replaced unless --force is explicitly used.
• CLI output now creates missing parent directories.

Try It

npm exec --yes --package=oss-signal@0.9.9 -- oss-signal --init

Review .github/workflows/oss-signal-trial.yml, commit it, and run the workflow
manually. No star, endorsement, or adoption claim is requested.

oss-signal v0.9.8

oss-signal v0.9.8 makes no-fail trial workflows produce a stronger evidence bundle in one run.

Added

• Generated trial workflows now upload both oss-signal-report.md and oss-signal-adoption-pack.md.
• Adoption packs now tell maintainers that the copied workflow publishes both artifacts without failing pull requests.
• Tests verify that generated trial workflows keep adoption evidence available while avoiding fail-under gates.

Verification

• npm run check
• node src/cli.js . --format workflow --output docs/examples/maintainer-trial-workflow.yml
• node src/cli.js platformatic/massimo --format adoption --output docs/examples/adoption-pack.md
• npm publish --dry-run

oss-signal v0.9.7

oss-signal v0.9.7 makes adoption packs easier to turn into public maintainer evidence.

Added

• Added a "Share Public Evidence" section to --format adoption.
• Added direct adoption-report and trial-feedback issue links for maintainers who run, review, reply, merge, or decline.
• Added a copyable evidence note with repository, evidence link, maintainer decision, and concrete outcome fields.
• Added tests that keep adoption packs focused on real maintainer decisions instead of stars, reciprocal work, or artificial engagement.

Verification

• npm run check
• node src/cli.js platformatic/massimo --format adoption --output docs/examples/adoption-pack.md
• npm publish --dry-run

oss-signal v0.9.6

oss-signal v0.9.6 makes adoption packs easier for external maintainers to answer.

Added

• Added a maintainer decision checklist to --format adoption.
• Added explicit response paths for no-fail workflow trials, focused PRs, documented not-applicable exceptions, and out-of-scope declines.
• Added a direct trial feedback issue link so maintainers can share useful negative or neutral feedback without treating it as adoption.
• Added tests that keep the adoption pack factual and response-oriented.

Verification

• npm run check
• node src/cli.js platformatic/massimo --format adoption --output docs/examples/adoption-pack.md
• npm publish --dry-run

oss-signal v0.9.5

oss-signal v0.9.5 adds adoption-pack output for low-risk maintainer trials.

Added

• Added --format adoption to produce a single Markdown pack with:
  • a clean npm trial command
  • a no-fail GitHub Actions workflow
  • a suggested maintainer message
  • current top findings
  • verification links and anti-spam boundaries
• Added GitHub Action support for format: adoption.
• Added tests that keep adoption packs factual and prevent overstated third-party adoption language.

Verification

• npm run check
• node src/cli.js SalmonPlays/oss-signal --format adoption
• npm publish --dry-run

oss-signal v0.9.4

oss-signal v0.9.4 expands the machine-readable output contract.

What Changed

• Added docs/schema/inventory-output.schema.json for --inventory --format json.
• Added docs/schema/rules-catalog.schema.json for --list-rules --format json.
• Added docs/examples/inventory-report.json as a committed inventory fixture.
• Added tests that parse the published schemas and JSON fixtures.

Verification

• npm run check
• npm publish --dry-run
• clean install smoke for oss-signal@0.9.4

oss-signal v0.9.3

oss-signal v0.9.3 adds explicit maintainer ownership to the rule catalog.

What Changed

• Added a maintainer-ownership check for MAINTAINERS.md, CODEOWNERS, .github/CODEOWNERS, or GOVERNANCE.md.
• Increased the transparent rule catalog to 16 rules and 110 weighted points.
• Refreshed citation metadata so the packaged repository metadata matches the current maintainer workflow.

Verification

• npm run check
• node src/cli.js --list-rules --format json
• node src/cli.js . --format markdown

oss-signal v0.9.2

oss-signal v0.9.2 adds a transparent rule catalog for maintainers and reviewers.

Changes

• Added --list-rules for printing the rule catalog without auditing a repository.
• Added --list-rules --format json for automation, dashboards, and reviewer checks.
• Added rules.md and examples/rules-catalog.json as committed fixtures.
• Made generated no-fail trial workflows render the current oss-signal Action tag from the package version.

Verification

• npm run check
• npm run evidence:verify
• npm publish --dry-run

oss-signal v0.9.1

oss-signal v0.9.1 adds compact maintainer triage output and improves package reviewer evidence.

Changes

• Added --format summary for a one-screen CLI and Action readout.
• Added summary-output.md and examples/github-summary.txt.
• Included the root REVIEWER_PACKET.md in the npm package tarball so reviewers can inspect the shortest evidence path from an installed package.
• Kept Markdown, JSON, SARIF, issue, plan, workflow, and inventory formats unchanged.

Verification

• npm run check
• npm publish --dry-run