@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 100 of 107)
| Version | Deps | Published |
|---|---|---|
| 4.88.4 | 3 / 5 | |
| 4.88.3 | 3 / 5 | |
| 4.88.2 | 3 / 5 | |
| 4.88.1 | 3 / 5 | |
| 4.88.0 | 3 / 5 | |
| 4.87.2 | 3 / 5 | |
| 4.87.1 | 3 / 5 | |
| 4.87.0 | 3 / 5 | |
| 4.86.1 | 3 / 5 | |
| 4.86.0 | 3 / 5 | |
| 4.84.1 | 3 / 5 | |
| 4.84.0 | 3 / 5 | |
| 4.83.2 | 3 / 5 | |
| 4.83.1 | 3 / 5 | |
| 4.83.0 | 3 / 5 | |
| 4.82.1 | 3 / 5 | |
| 4.82.0 | 3 / 5 | |
| 4.81.6 | 3 / 5 | |
| 4.81.3 | 3 / 5 | |
| 4.81.2 | 3 / 5 | |
| 4.81.1 | 3 / 5 | |
| 4.81.0 | 3 / 5 | |
| 4.80.0 | 3 / 5 | |
| 4.79.0 | 3 / 5 | |
| 4.78.0 | 3 / 5 | |
| 4.77.1 | 3 / 5 | |
| 4.77.0 | 3 / 5 | |
| 4.76.0 | 3 / 5 | |
| 4.75.4 | 3 / 5 | |
| 4.75.3 | 3 / 5 | |
| 4.75.2 | 3 / 5 | |
| 4.75.1 | 3 / 5 | |
| 4.75.0 | 3 / 5 | |
| 4.74.0 | 3 / 5 | |
| 4.73.0 | 3 / 5 | |
| 4.72.0 | 3 / 5 | |
| 4.71.1 | 3 / 5 | |
| 4.71.0 | 3 / 5 | |
| 4.70.1 | 3 / 5 | |
| 4.70.0 | 3 / 5 | |
| 4.69.0 | 3 / 5 | |
| 4.68.0 | 3 / 5 | |
| 4.67.0 | 3 / 5 | |
| 4.66.4 | 3 / 5 | |
| 4.66.3 | 3 / 5 | |
| 4.66.2 | 3 / 5 | |
| 4.66.1 | 3 / 5 | |
| 4.66.0 | 3 / 5 | |
| 4.65.0 | 3 / 5 | |
| 4.64.0 | 3 / 5 | |
| 4.63.2 | 3 / 5 | |
| 4.63.1 | 3 / 5 | |
| 4.63.0 | 3 / 5 | |
| 4.62.2 | 3 / 5 | |
| 4.62.1 | 3 / 5 | |
| 4.62.0 | 3 / 5 | |
| 4.61.0 | 3 / 5 | |
| 4.60.1 | 3 / 5 | |
| 4.60.0 | 3 / 5 | |
| 4.59.1 | 3 / 5 | |
| 4.59.0 | 3 / 5 | |
| 4.58.0 | 3 / 5 | |
| 4.57.1 | 3 / 5 | |
| 4.57.0 | 3 / 5 | |
| 4.56.0 | 3 / 5 | |
| 4.55.0 | 3 / 5 | |
| 4.54.1 | 3 / 5 | |
| 4.54.0 | 3 / 5 | |
| 4.53.1 | 3 / 5 | |
| 4.53.0 | 3 / 5 | |
| 4.52.4 | 3 / 5 | |
| 4.52.1 | 3 / 5 | |
| 4.52.0 | 3 / 5 | |
| 4.41.0 | 2 / 5 | |
| 4.40.0 | 2 / 5 | |
| 4.39.0 | 2 / 5 | |
| 4.38.0 | 2 / 5 | |
| 4.37.0 | 2 / 5 | |
| 4.36.1 | 2 / 5 | |
| 4.36.0 | 2 / 5 | |
| 4.35.1 | 2 / 5 | |
| 4.35.0 | 2 / 7 | |
| 4.34.1 | 2 / 7 | |
| 4.34.0 | 2 / 7 | |
| 4.33.0 | 2 / 7 | |
| 4.32.0 | 2 / 7 | |
| 4.31.2 | 2 / 7 | |
| 4.31.1 | 2 / 7 | |
| 4.31.0 | 2 / 7 | |
| 4.30.0 | 2 / 7 | |
| 4.29.0 | 2 / 7 | |
| 4.28.3 | 2 / 7 | |
| 4.28.2 | 2 / 7 | |
| 4.7.0 | 2 / 7 | |
| 4.6.1 | 2 / 7 | |
| 4.6.0 | 2 / 7 | |
| 4.5.1 | 2 / 7 | |
| 4.5.0 | 2 / 7 | |
| 4.4.1 | 2 / 7 | |
| 4.4.0 | 2 / 7 |
v4.30.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.29.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.28.3
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.28.2
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.7.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.6.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.6.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.5.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.5.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.4.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.4.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.