gh-history
generate github history into md file
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:request | AI (dependencies): The `request` package is a well-known HTTP library; its use in a GitHub history generator is appropriate and poses no material risk despite being deprecated. | ai | |
| provenance | no-provenance | AI (provenance): Package predates npm provenance attestation by years; absence is expected and not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a legitimate CLI dependency declared in package.json; phantom detection is a false positive for this CLI tool. | ai | |
| phantom-deps | phantom-dep:modulex-promise | AI (phantom-deps): modulex-promise is a legitimate dependency from the same publisher ecosystem; phantom detection is a false positive here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.5 | 5 / 0 | |
| 1.0.4 | 5 / 0 | |
| 1.0.3 | 5 / 0 | |
| 1.0.2 | 5 / 0 | |
| 1.0.1 | 6 / 0 |
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.