@highstate/git
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tar | AI (phantom-deps): Declared and used; phantom-dep heuristic is not allowed to block. | ai | |
| phantom-deps | phantom-dep:remeda | AI (phantom-deps): Declared and used; phantom-dep heuristic is not allowed to block. | ai | |
| phantom-deps | phantom-dep:@highstate/contract | AI (phantom-deps): Declared and used; phantom-dep heuristic is not allowed to block. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected for internal tooling. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @highstate/git is a Git-operations library in the highstate-io monorepo; not a typosquat of 'got'. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): 2-edit distance to 'vite' is coincidental; package is clearly a Git integration module. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.21.1 | 8 / 3 | |
| 0.20.0 | 7 / 3 | |
| 0.19.1 | 7 / 3 | |
| 0.18.0 | 7 / 3 | |
| 0.17.0 | 7 / 3 | |
| 0.16.0 | 7 / 3 | |
| 0.15.0 | 7 / 3 | |
| 0.14.2 | 7 / 3 | |
| 0.14.0 | 7 / 3 | |
| 0.13.2 | 7 / 3 | |
| 0.13.1 | 7 / 3 | |
| 0.13.0 | 7 / 3 | |
| 0.12.1 | 7 / 3 | |
| 0.12.0 | 7 / 3 | |
| 0.11.7 | 7 / 3 | |
| 0.11.6 | 7 / 3 | |
| 0.11.5 | 7 / 3 | |
| 0.11.4 | 7 / 3 | |
| 0.11.3 | 7 / 3 | |
| 0.10.0 | 7 / 3 | |
| 0.9.37 | 7 / 3 | |
| 0.9.36 | 7 / 3 | |
| 0.9.35 | 7 / 3 | |
| 0.9.34 | 7 / 3 | |
| 0.9.33 | 7 / 3 | |
| 0.9.32 | 7 / 3 | |
| 0.9.31 | 7 / 3 | |
| 0.9.30 | 7 / 3 | |
| 0.9.29 | 7 / 3 | |
| 0.9.28 | 7 / 3 | |
| 0.9.27 | 7 / 3 | |
| 0.9.26 | 7 / 3 | |
| 0.9.25 | 7 / 3 | |
| 0.9.24 | 7 / 3 | |
| 0.9.23 | 7 / 3 | |
| 0.9.22 | 7 / 3 | |
| 0.9.21 | 7 / 3 | |
| 0.9.20 | 7 / 1 | |
| 0.9.19 | 7 / 1 | |
| 0.9.18 | 7 / 1 | |
| 0.9.16 | 7 / 1 |
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.