@metamask/smart-accounts-kit
Toolkit for managing and interacting with MetaMask Smart Accounts, built on Viem
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index-X7Qn3JTg.d.cts | AI (source-diff): TypeScript declaration file (.d.cts) with long lines from bundled type signatures; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-DUJmm8Wz.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type signatures; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-G78z6nwi.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; standard tsup build artifact for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are dist artifacts (sourcemaps, declaration files) consistent with build output growth for this package. | ai | |
| source-diff | obfuscated-file:dist/index-DfDAuvr5.d.cts | AI (source-diff): TypeScript declaration file with long lines from bundled type exports; standard tsup build artifact for this package. | ai | |
| source-diff | obfuscated-file:dist/index-BToRQKyJ.d.cts | AI (source-diff): TypeScript declaration file with long lines from bundled type unions; not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/index-Cg-JakqA.d.ts | AI (source-diff): TypeScript declaration file with long lines from bundled type unions; not obfuscated code. | ai | |
| dependencies | unvetted-dep:ox | AI (dependencies): ox is a well-known Ethereum utility library from the Viem/Wevm ecosystem; appropriate dependency for this MetaMask smart accounts toolkit. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is declared in dependencies and referenced in lavamoat allowScripts config; stable false positive for this package. | ai | |
| license | uncommon-license:MIT-0 | AI (license): MIT-0 OR Apache-2.0 is a permissive dual-license; stable for this MetaMask package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 7 / 29 | |
| 1.5.0 | 6 / 29 | |
| 1.4.0 | 6 / 29 | |
| 1.3.0 | 6 / 29 | |
| 1.2.0 | 6 / 29 | |
| 1.1.0 | 6 / 28 | |
| 1.0.0 | 6 / 28 | |
| 0.3.0 | 6 / 23 | |
| 0.2.0 | 6 / 23 | |
| 0.1.0 | 6 / 23 |
v1.6.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.