@circle-fin/developer-controlled-wallets
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 | net-exec-file:dist/developer-controlled-wallets.cjs.js | AI (source-diff): Minified rollup bundle of axios + Node built-ins; no dropper/loader behavior, standard SDK dist artifact. | ai | |
| source-diff | net-exec-file:dist/developer-controlled-wallets.es.js | AI (source-diff): ESM variant of same rollup bundle; same rationale as CJS file. | ai | |
| source-diff | obfuscated-file:dist/developer-controlled-wallets.es.js | AI (source-diff): Long lines are minified rollup output, not obfuscation; stable pattern for this SDK. | ai | |
| source-diff | obfuscated-file:dist/types/clients/core.d.ts | AI (source-diff): TypeScript declaration file with long lines; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/types/clients/developer-controlled-wallets.d.ts | AI (source-diff): TypeScript declaration file with long lines; not obfuscated code. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 10.3.1 | 1 / 9 | |
| 10.3.0 | 1 / 10 | |
| 10.2.0 | 1 / 9 | |
| 10.1.0 | 1 / 9 | |
| 10.0.1 | 1 / 9 | |
| 10.0.0 | 1 / 9 | |
| 9.6.0 | 1 / 9 | |
| 9.5.0 | 1 / 9 | |
| 9.4.0 | 1 / 9 | |
| 9.3.0 | 1 / 9 | |
| 9.2.1 | 1 / 9 |
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
6 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.
v10.1.0
6 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.
v10.0.1
6 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.