@crossmint/wallets-sdk
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 | obfuscated-file:dist/types-5kZcVs3E.d.cts | AI (source-diff): TypeScript declaration file with long import lines from generated API types; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-CRMCeDuN.d.ts | AI (source-diff): TypeScript declaration file with long import lines from generated API types; not executable obfuscated code. | ai | |
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead is a minor metadata gap, not a supply chain risk for this publisher. | ai | |
| source-diff | obfuscated-file:dist/types-BZ83dAVx.d.ts | AI (source-diff): TypeScript declaration file with long generated import lines; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-fUCYdXAl.d.cts | AI (source-diff): TypeScript declaration file with long generated import lines; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-Nc5kinaI.d.cts | AI (source-diff): TypeScript declaration file with long generated import lines; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-NmTwqiYW.d.ts | AI (source-diff): TypeScript declaration file with long generated import lines; not executable obfuscated code. | ai | |
| provenance | publisher-changed | AI (provenance): albertoelias-xm is a Crossmint org publisher with 96 approved packages; transition appears legitimate. | ai | |
| phantom-deps | phantom-dep:@stellar/stellar-sdk | AI (phantom-deps): Newly added runtime dep for Stellar support; phantom-dep fires due to config-level reference rather than direct import. | ai | |
| phantom-deps | phantom-dep:tweetnacl | AI (phantom-deps): tweetnacl is a declared runtime dep used in bundled output; phantom-dep heuristic fires due to indirect import pattern. | ai | |
| source-diff | obfuscated-file:dist/types-a9zAn0G2.d.ts | AI (source-diff): TypeScript declaration file with long import lines; not executable code, no obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-r-OYYHDs.d.cts | AI (source-diff): TypeScript declaration file with long import lines; not executable code, no obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-DZWn68Po.d.cts | AI (source-diff): TypeScript declaration file with long import lines from generated API client; not executable obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types-CtOIG5sn.d.ts | AI (source-diff): TypeScript declaration file with long import lines from generated API client; not executable obfuscated code. | ai | |
| dependencies | unvetted-dep:ox | AI (dependencies): ox is a legitimate Ethereum primitives library from the viem/wagmi ecosystem; stable dependency for this wallet SDK. | ai | |
| phantom-deps | phantom-dep:base32.js | AI (phantom-deps): base32.js is declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 14 / 4 | |
| 1.3.0 | 14 / 4 | |
| 1.2.0 | 14 / 4 | |
| 1.1.2 | 14 / 4 | |
| 1.1.1 | 14 / 4 | |
| 1.1.0 | 14 / 4 | |
| 1.0.15 | 14 / 4 | |
| 1.0.14 | 14 / 4 | |
| 1.0.13 | 14 / 4 | |
| 1.0.12 | 14 / 4 | |
| 1.0.11 | 14 / 4 | |
| 1.0.10 | 14 / 4 | |
| 1.0.9 | 14 / 4 | |
| 1.0.8 | 14 / 4 | |
| 1.0.7 | 14 / 4 | |
| 1.0.5 | 14 / 4 | |
| 1.0.4 | 14 / 4 | |
| 1.0.3 | 14 / 4 | |
| 1.0.2 | 14 / 4 | |
| 1.0.1 | 14 / 4 | |
| 0.21.1 | 12 / 4 | |
| 0.21.0 | 13 / 4 | |
| 0.20.2 | 12 / 4 | |
| 0.20.1 | 12 / 4 | |
| 0.20.0 | 12 / 4 | |
| 0.19.0 | 12 / 4 | |
| 0.18.15 | 12 / 4 | |
| 0.18.14 | 12 / 4 | |
| 0.18.13 | 12 / 4 | |
| 0.18.12 | 12 / 4 | |
| 0.18.11 | 13 / 4 | |
| 0.18.10 | 13 / 4 | |
| 0.18.9 | 13 / 4 | |
| 0.18.8 | 13 / 4 | |
| 0.18.7 | 13 / 4 | |
| 0.18.6 | 13 / 4 | |
| 0.18.4 | 12 / 4 | |
| 0.18.3 | 12 / 4 | |
| 0.18.2 | 12 / 4 |
v1.4.0
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.15
3 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.12
4 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.
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.11
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. 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.18.15
2 findingsThis version was published by a different npm account than previous versions on 2026-01-22. 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.18.14
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. 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.18.13
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. 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.18.12
2 findingsThis version was published by a different npm account than previous versions on 2025-12-23. 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.18.11
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. 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.18.10
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. 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.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.