@identity-connect/crypto
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped Aptos Labs crypto package; Levenshtein match to bcrypt is coincidental, not a squatting attempt. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard base64 decode utility with no obfuscation or network exfiltration; stable pattern for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 4 / 8 | |
| 0.3.0 | 4 / 8 | |
| 0.2.11 | 4 / 10 | |
| 0.2.10 | 4 / 10 | |
| 0.2.9 | 4 / 10 | |
| 0.2.8 | 4 / 10 | |
| 0.2.7 | 4 / 10 |
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.