isomorphic-git
A pure JavaScript reimplementation of git for node and browsers
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:minimisted | AI (dependencies): minimisted is a long-standing declared dependency of isomorphic-git; not a new or suspicious addition. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of Sigstore provenance is not a risk signal here. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in isomorphic-git is used for SHA checksum handling in git object packing — a core, legitimate operation. Not a malicious payload indicator for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.38.1 | 11 / 48 | |
| 1.37.7 | 11 / 48 | |
| 1.37.4 | 11 / 48 | |
| 1.37.0 | 11 / 48 | |
| 1.34.2 | 13 / 69 | |
| 1.32.2 | 12 / 68 | |
| 1.32.1 | 12 / 68 | |
| 1.32.0 | 12 / 68 | |
| 1.31.1 | 12 / 68 | |
| 1.30.3 | 12 / 68 |
v1.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.