@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): Crypto dep used indirectly; not a security concern. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Legit initial version of long-established, high-trust package. | ai | |
| source-diff | obfuscated-file:dist/esm/provider-D-0RYJqt.mjs | AI (source-diff): ESM equivalent of same minified build output. | ai | |
| source-diff | obfuscated-file:dist/esm/rainbow-kit.mjs | AI (source-diff): ESM equivalent of same minified build output. | ai | |
| source-diff | obfuscated-file:dist/cjs/provider-CCUYFoYv.js | AI (source-diff): Minified rollup/terser build output implementing documented cross-app crypto flow, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/rainbow-kit.js | AI (source-diff): Minified rollup/terser build output implementing RainbowKit connector, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/provider.mjs | AI (source-diff): Standard minified rollup build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/connector.js | AI (source-diff): Standard minified rollup build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/provider.js | AI (source-diff): Standard minified rollup build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/connector.mjs | AI (source-diff): Standard minified rollup build output, not obfuscation. | ai | |
| 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 | |
| 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 | |
| dependencies | unvetted-dep:@privy-io/encoding | AI (dependencies): First-party privy.io dependency; stable pattern across this package's versions. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 6 / 18 | |
| 0.5.15 | 6 / 18 | |
| 0.5.14 | 6 / 18 | |
| 0.5.13 | 6 / 18 | |
| 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 | |
| 0.2.0 | 4 / 16 | |
| 0.1.8 | 3 / 16 | |
| 0.1.7 | 3 / 17 | |
| 0.1.6 | 3 / 13 | |
| 0.1.5 | 3 / 13 | |
| 0.1.4 | 3 / 13 | |
| 0.1.3 | 3 / 13 | |
| 0.1.2 | 3 / 13 | |
| 0.1.1 | 3 / 10 | |
| 0.1.0 | 3 / 10 | |
| 0.0.8 | 3 / 10 | |
| 0.0.7 | 3 / 10 | |
| 0.0.6 | 3 / 10 | |
| 0.0.5 | 3 / 10 | |
| 0.0.4 | 3 / 10 | |
| 0.0.3 | 3 / 10 | |
| 0.0.2 | 3 / 10 | |
| 0.0.1 | 3 / 10 | |
| 0.0.0 | 3 / 10 |
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.