@remix-project/remix-lib
Library to various Remix tools
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(hex) used for EVM transaction encoding — standard pattern in this Ethereum tooling library. | ai | |
| phantom-deps | phantom-dep:events | AI (phantom-deps): Common polyfill dep in Ethereum monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/mpt | AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/blockchain | AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/statemanager | AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.5.100 | 21 / 9 | |
| 0.5.98 | 21 / 9 | |
| 0.5.97 | 19 / 9 | |
| 0.5.96 | 13 / 9 | |
| 0.5.95 | 13 / 9 | |
| 0.5.93 | 13 / 9 | |
| 0.5.92 | 13 / 9 | |
| 0.5.91 | 13 / 9 | |
| 0.5.90 | 13 / 9 | |
| 0.5.89 | 13 / 9 | |
| 0.5.88 | 13 / 9 | |
| 0.5.87 | 15 / 9 | |
| 0.5.86 | 15 / 9 | |
| 0.5.85 | 15 / 9 | |
| 0.5.84 | 15 / 9 | |
| 0.5.83 | 15 / 9 | |
| 0.5.82 | 15 / 9 | |
| 0.5.81 | 15 / 9 | |
| 0.5.80 | 15 / 9 | |
| 0.5.79 | 15 / 9 | |
| 0.5.78 | 15 / 9 | |
| 0.5.77 | 14 / 9 | |
| 0.5.76 | 14 / 9 |
v0.5.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.