@bonfida/spl-name-service
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/node_modules/js-base64/base64.js | AI (source-diff): Minified rollup bundle of js-base64; content is standard base64 encoding logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/esm/node_modules/js-base64/base64.js | AI (source-diff): ESM variant of same minified js-base64 bundle; benign. | ai | |
| source-diff | obfuscated-file:dist/cjs/constants.js | AI (source-diff): Minified constants file containing Solana PublicKey addresses; no obfuscation or malicious logic. | ai | |
| source-diff | obfuscated-file:dist/esm/constants.js | AI (source-diff): ESM variant of same constants file; benign Solana address data. | ai | |
| phantom-deps | phantom-dep:@scure/base | AI (phantom-deps): Same rollup bundling pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): Same rollup bundling pattern; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Solana SDK; sparse README is typical for developer-focused crypto libraries, not spam. | ai | |
| phantom-deps | phantom-dep:@solana/spl-token | AI (phantom-deps): Same rollup bundling pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:graphemesplit | AI (phantom-deps): Same rollup bundling pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:borsh | AI (phantom-deps): Bundled via rollup; declared as runtime dep but resolved at build time — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:punycode | AI (phantom-deps): Same rollup bundling pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:ipaddr.js | AI (phantom-deps): Same rollup bundling pattern; stable false positive. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.23 | 9 / 32 | |
| 3.0.22 | 9 / 32 | |
| 3.0.21 | 9 / 32 | |
| 3.0.20 | 9 / 32 | |
| 3.0.19 | 9 / 32 | |
| 3.0.18 | 9 / 31 | |
| 3.0.17 | 9 / 31 | |
| 3.0.16 | 9 / 31 | |
| 3.0.15 | 9 / 31 | |
| 3.0.14 | 9 / 31 | |
| 3.0.13 | 9 / 31 | |
| 3.0.12 | 9 / 31 | |
| 3.0.11 | 9 / 31 |
v3.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.16
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.
v3.0.15
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.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.