git-diff
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Historical change from 2018, stable 3054 days, not a fresh takeover signal. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Same stale 2018 publisher change, long-stable, no material code diff. | ai | |
| dependencies | unvetted-dep:shelljs.exec | AI (dependencies): git-diff legitimately uses shelljs.exec to invoke git; stable dependency for this package's core functionality. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 5 / 12 | |
| 2.0.6 | 5 / 12 | |
| 2.0.5 | 5 / 12 | |
| 2.0.4 | 5 / 12 | |
| 2.0.3 | 5 / 12 | |
| 2.0.2 | 5 / 12 | |
| 2.0.1 | 5 / 12 | |
| 2.0.0 | 5 / 12 |
v2.0.7
2 findingsThis version was published by a different npm account than previous versions on 2026-06-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
2 findingsThis version was published by a different npm account (danday74) than the most recent previously approved version (daniel-lewis-bsc-hons) on 2018-03-09. It has since remained available on npm for 3054 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.