ghrepos
Interact with the GitHub repos API
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package uses semantic-release via GitHub Actions CI/CD; publisher change from human account to GitHub Actions is the expected and documented automation pattern for this repo. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP (127.0.0.1) appears only in test.js as a mock HTTP server for pagination testing — not production code or exfiltration. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 1 / 9 | |
| 3.0.1 | 1 / 9 | |
| 3.0.0 | 1 / 9 | |
| 2.1.0 | 1 / 4 | |
| 2.0.0 | 1 / 3 | |
| 1.5.0 | 1 / 3 | |
| 1.4.0 | 1 / 3 | |
| 1.3.1 | 1 / 3 | |
| 1.3.0 | 1 / 3 | |
| 1.2.0 | 1 / 3 | |
| 1.1.1 | 1 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.5 | 3 / 3 | |
| 1.0.4 | 3 / 3 | |
| 1.0.3 | 2 / 3 | |
| 1.0.2 | 2 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
v3.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-12-23. This could indicate a legitimate maintainer transition or an account compromise.