@explorins/web3-ts
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/types/utils/http-client.js | AI (source-diff): Standard browser/Node HTTP client using fetch and dynamic require for bundler compatibility; no malicious payload. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 148 versions; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 36 of 136)
| Version | Deps | Published |
|---|---|---|
| 0.2.6 | 14 / 1 | |
| 0.2.5 | 14 / 1 | |
| 0.2.4 | 14 / 1 | |
| 0.2.2 | 14 / 1 | |
| 0.2.1 | 14 / 1 | |
| 0.2.0 | 14 / 1 | |
| 0.1.76 | 11 / 0 | |
| 0.1.75 | 11 / 0 | |
| 0.1.74 | 11 / 0 | |
| 0.1.73 | 11 / 0 | |
| 0.1.72 | 11 / 0 | |
| 0.1.71 | 11 / 0 | |
| 0.1.70 | 11 / 0 | |
| 0.1.69 | 10 / 0 | |
| 0.1.68 | 10 / 0 | |
| 0.1.67 | 10 / 0 | |
| 0.1.66 | 10 / 0 | |
| 0.1.65 | 10 / 0 | |
| 0.1.64 | 10 / 0 | |
| 0.1.63 | 10 / 0 | |
| 0.1.62 | 10 / 0 | |
| 0.1.61 | 10 / 0 | |
| 0.1.60 | 10 / 0 | |
| 0.1.59 | 9 / 0 | |
| 0.1.58 | 9 / 0 | |
| 0.1.57 | 8 / 0 | |
| 0.1.56 | 8 / 0 | |
| 0.1.55 | 8 / 0 | |
| 0.1.54 | 8 / 0 | |
| 0.1.53 | 8 / 0 | |
| 0.1.52 | 8 / 0 | |
| 0.1.51 | 8 / 0 | |
| 0.1.40 | 8 / 0 | |
| 0.1.39 | 8 / 0 | |
| 0.1.38 | 8 / 0 | |
| 0.1.5 | 8 / 0 |
v0.1.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.