Repository: /Users/amon/Documents/Codex/2026-06-01/openai-s/outputs/oss-signal
Source: local
Generated: 2026-06-05T15:57:18.730Z
Score: 100/100 (A)
| Status | Check | Why it matters |
|---|---|---|
| PASS | README | A clear README is the front door for users and contributors. |
| PASS | License | A license tells downstream users what they may legally do with the code. |
| PASS | Contributing guide | Maintainers get better issues and pull requests when expectations are documented. |
| PASS | Security policy | Responsible disclosure needs a private, documented path. |
| PASS | Code of conduct | Community norms reduce ambiguity during difficult interactions. |
| PASS | Changelog | Users need a durable place to understand release impact. |
| PASS | Support policy | Support boundaries help maintainers avoid turning every request into unpaid consulting. |
| PASS | Continuous integration | CI catches regressions before maintainers merge changes. |
| PASS | Tests | Tests make review safer and lower the cost of outside contributions. |
| PASS | Issue templates | Issue templates collect the facts maintainers need to reproduce and triage. |
| PASS | Pull request template | PR templates nudge contributors to include tests, docs, and review context. |
| PASS | Dependency update automation | Automated dependency updates reduce security and compatibility drift. |
| PASS | Static security analysis | Static analysis finds common vulnerability patterns before releases. |
| PASS | Node package metadata | Package metadata makes installation, testing, and release automation discoverable. |
| PASS | Dependency lockfile | Lockfiles make CI and contributor setup reproducible. |
No missing checks. Keep the report current as the repository evolves.