@li0ard/gost
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:got | AI (typosquat): GOST crypto library; name derives from the Russian standard, not a typo of 'got'. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): GOST crypto library; no relation to 'jest', 2-edit distance is coincidental. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.5 | 2 / 4 | |
| 0.1.4 | 2 / 2 | |
| 0.1.3 | 2 / 2 | |
| 0.1.2 | 2 / 2 | |
| 0.0.1 | 0 / 0 |
v0.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.4
2 findingsPackage name '@li0ard/gost' is 1 edit(s) away from popular package 'got'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
2 findingsPackage name '@li0ard/gost' is 1 edit(s) away from popular package 'got'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
2 findingsPackage name '@li0ard/gost' is 1 edit(s) away from popular package 'got'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
2 findingsPackage name '@li0ard/gost' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.