@remix-project/remix-simulator
Ethereum IDE and tools for the web
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@ethereumjs/tx | AI (npm-metadata): Fork owned by yann300 (listed Remix contributor); appears to be a temporary v10 compatibility patch within the trusted project org. | ai | |
| phantom-deps | phantom-dep:rlp | AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Declared dep used by bin/ethsim CLI entry; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ethjs-util | AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:string-similarity | AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.2.91 | 25 / 9 | |
| 0.2.90 | 25 / 9 | |
| 0.2.89 | 25 / 9 | |
| 0.2.88 | 25 / 9 | |
| 0.2.87 | 23 / 9 | |
| 0.2.86 | 23 / 9 | |
| 0.2.85 | 23 / 9 | |
| 0.2.84 | 23 / 9 | |
| 0.2.83 | 23 / 9 | |
| 0.2.82 | 23 / 9 | |
| 0.2.81 | 23 / 9 | |
| 0.2.80 | 25 / 9 | |
| 0.2.79 | 25 / 9 | |
| 0.2.78 | 25 / 9 | |
| 0.2.77 | 25 / 9 | |
| 0.2.76 | 25 / 9 | |
| 0.2.75 | 25 / 9 | |
| 0.2.74 | 25 / 9 | |
| 0.2.73 | 25 / 9 | |
| 0.2.72 | 25 / 9 | |
| 0.2.71 | 25 / 9 | |
| 0.2.70 | 25 / 9 | |
| 0.2.69 | 25 / 9 | |
| 0.2.68 | 24 / 9 | |
| 0.2.67 | 24 / 9 | |
| 0.2.66 | 24 / 9 | |
| 0.2.65 | 24 / 9 | |
| 0.2.64 | 24 / 9 | |
| 0.2.63 | 24 / 9 | |
| 0.2.62 | 24 / 9 | |
| 0.2.61 | 24 / 9 | |
| 0.2.60 | 24 / 9 | |
| 0.2.59 | 24 / 9 | |
| 0.2.58 | 24 / 9 | |
| 0.2.57 | 24 / 9 | |
| 0.2.56 | 24 / 9 | |
| 0.2.55 | 24 / 9 | |
| 0.2.54 | 24 / 9 | |
| 0.2.53 | 24 / 9 | |
| 0.2.52 | 24 / 9 | |
| 0.2.51 | 23 / 9 | |
| 0.2.50 | 23 / 9 | |
| 0.2.49 | 23 / 9 | |
| 0.2.48 | 23 / 9 | |
| 0.2.47 | 23 / 9 | |
| 0.2.46 | 23 / 9 | |
| 0.2.45 | 23 / 9 |
v0.2.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.