@circle-fin/user-controlled-wallets
This SDK provides convenient access to Circle's User Controlled Wallets APIs for applications written in NodeJS. For the API reference, see the [Circle Web3 API docs](https://developers.circle.com/api-reference/wallets/common/ping).
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/user-controlled-wallets.cjs.js | AI (source-diff): Minified rollup bundle of axios + SDK; network imports are axios HTTP client, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/user-controlled-wallets.es.js | AI (source-diff): Same minified rollup bundle (ESM variant); false positive for the same reason. | ai | |
| source-diff | obfuscated-file:dist/user-controlled-wallets.es.js | AI (source-diff): Long lines are standard rollup minification output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types/clients/core.d.ts | AI (source-diff): TypeScript declaration file with long lines from auto-generated OpenAPI types; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/types/clients/user-controlled-wallets.d.ts | AI (source-diff): Auto-generated OpenAPI TypeScript declarations; long lines are expected, not malicious. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 10.6.0 | 1 / 9 | |
| 10.5.5 | 1 / 9 | |
| 10.5.4 | 1 / 9 | |
| 10.5.1 | 1 / 9 | |
| 10.5.0 | 1 / 9 | |
| 10.4.0 | 1 / 9 | |
| 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 |
v10.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.