@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, 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher is long-tenured known maintainer of the Remix project. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/vm | AI (phantom-deps): Legit ethereum tooling dep, likely used via re-export/build; stable across versions. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Old publisher change (2021), long stable availability, established maintainer track record. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/blockchain | AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. | ai | |
| 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:@ethereumjs/statemanager | AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. | 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 |
Versions (showing 6 of 106)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 9 / 9 | |
| 0.4.34 | 9 / 9 | |
| 0.4.33 | 9 / 9 | |
| 0.4.32 | 9 / 9 | |
| 0.4.31 | 9 / 9 | |
| 0.4.30 | 9 / 9 |
v0.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yann300) than the most recent previously approved version (aniket-engg) on 2021-06-10, but yann300 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.