@account-kit/smart-contracts
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:src/light-account/accounts/predictAddress.ts | AI (source-diff): EVM proxy initcode bytecode hex literal; standard pattern in smart contract SDKs for address prediction. | ai | |
| source-diff | encoded-string-file:dist/esm/src/light-account/accounts/predictAddress.js | AI (source-diff): EVM proxy initcode bytecode constant; standard pattern for smart-contract SDKs across all versions. | ai | |
| source-diff | encoded-string-file:dist/esm/src/ma-v2/utils.js | AI (source-diff): EVM utility contract bytecode constant; standard pattern for smart-contract SDKs across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Alchemy monorepo package; no provenance is consistent across all versions and poses no security risk here. | ai |
Versions (showing 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 2 / 7 | |
| 4.3.0 | 2 / 7 | |
| 4.2.0 | 2 / 7 | |
| 4.1.1 | 2 / 7 | |
| 4.1.0 | 2 / 7 | |
| 4.0.1 | 2 / 7 | |
| 4.0.0 | 2 / 7 |
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.