@neuraiproject/neurai-key
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/NeuraiKey.js | AI (source-diff): Long hex strings are DH prime constants in the browserified crypto bundle, not obfuscated payloads. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is standard BIP39 seed-to-HDKey conversion; not obfuscation or payload hiding. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 5 / 10 | |
| 3.1.0 | 5 / 10 | |
| 3.0.2 | 5 / 10 | |
| 3.0.1 | 5 / 10 | |
| 3.0.0 | 5 / 10 | |
| 2.8.8 | 6 / 10 | |
| 2.8.7 | 4 / 8 | |
| 2.8.6 | 5 / 8 | |
| 2.8.5 | 5 / 8 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.7
2 findingsModified file contains 7 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.