@privy-io/cross-app-connect
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established privy.io org package with 83 versions; dormancy likely reflects release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@privy-io/popup | AI (dependencies): First-party privy.io dependency; stable pattern across this package's versions. | ai | |
| dependencies | unvetted-dep:@privy-io/encoding | AI (dependencies): First-party privy.io dependency; stable pattern across this package's versions. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): @noble/hashes is listed as a direct dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.5.12 | 6 / 18 | |
| 0.5.11 | 6 / 18 | |
| 0.5.10 | 6 / 18 | |
| 0.5.9 | 6 / 18 | |
| 0.5.8 | 6 / 18 | |
| 0.5.7 | 6 / 17 | |
| 0.5.6 | 5 / 17 | |
| 0.5.3 | 5 / 17 | |
| 0.4.0 | 4 / 18 | |
| 0.3.5 | 4 / 18 | |
| 0.3.4 | 4 / 18 | |
| 0.3.3 | 4 / 18 | |
| 0.3.2 | 4 / 18 | |
| 0.3.1 | 4 / 18 | |
| 0.3.0 | 4 / 17 | |
| 0.2.3 | 4 / 16 | |
| 0.2.2 | 4 / 16 |
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: privy-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.