@privy-io/node
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:resources/wallets/wallets.js | AI (source-diff): Hex string is a documentation example in a JSDoc comment, not an executable payload. | ai | |
| source-diff | encoded-string-file:resources/wallets/wallets.mjs | AI (source-diff): Same JSDoc example hex string in ESM variant; not executable. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @privy-io/node is not a typosquat of zod; Levenshtein match is spurious. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding of cryptographic keys is core functionality of this wallet/crypto SDK. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of wallet entropy is expected in a crypto/wallet SDK. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 9 / 0 | |
| 0.18.0 | 9 / 0 | |
| 0.17.0 | 9 / 0 | |
| 0.16.0 | 9 / 0 | |
| 0.15.0 | 9 / 0 | |
| 0.14.0 | 9 / 0 | |
| 0.13.0 | 9 / 0 | |
| 0.10.1 | 9 / 0 | |
| 0.10.0 | 9 / 0 | |
| 0.9.0 | 9 / 0 | |
| 0.8.0 | 9 / 0 | |
| 0.7.0 | 9 / 0 | |
| 0.6.2 | 9 / 0 | |
| 0.6.1 | 9 / 0 | |
| 0.6.0 | 9 / 0 | |
| 0.5.0 | 9 / 0 | |
| 0.4.1 | 9 / 0 | |
| 0.4.0 | 9 / 0 | |
| 0.3.0 | 9 / 0 | |
| 0.2.0 | 8 / 0 | |
| 0.1.0 | 8 / 0 |
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.18.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.