@remix-project/remix-debug
Tool to debug Ethereum transactions
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 Remix core maintainer yann300; consistent with project's pattern of patching upstream ethereumjs deps. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:merge | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ansi-gray | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:deep-equal | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ethjs-util | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:express-ws | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Decodes EVM bytecode hex strings for opcode analysis — core debugger functionality, not malicious. | ai | |
| phantom-deps | phantom-dep:color-support | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/tx | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/vm | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/block | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:string-similarity | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@remix-project/remix-simulator | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic not applicable here. | ai | |
| phantom-deps | phantom-dep:time-stamp | AI (phantom-deps): Monorepo config artifact; stable false positive for this package. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 0.5.91 | 22 / 10 | |
| 0.5.90 | 22 / 10 | |
| 0.5.89 | 22 / 10 | |
| 0.5.88 | 22 / 10 | |
| 0.5.87 | 21 / 10 | |
| 0.5.86 | 21 / 10 | |
| 0.5.85 | 21 / 10 | |
| 0.5.84 | 21 / 10 | |
| 0.5.83 | 21 / 10 | |
| 0.5.82 | 21 / 10 | |
| 0.5.81 | 21 / 10 | |
| 0.5.80 | 22 / 10 | |
| 0.5.79 | 22 / 10 | |
| 0.5.78 | 22 / 10 | |
| 0.5.77 | 22 / 10 | |
| 0.5.76 | 22 / 10 | |
| 0.5.75 | 22 / 10 | |
| 0.5.74 | 22 / 10 | |
| 0.5.73 | 22 / 10 | |
| 0.5.72 | 22 / 10 | |
| 0.5.71 | 22 / 10 | |
| 0.5.70 | 22 / 10 | |
| 0.5.69 | 21 / 10 | |
| 0.5.68 | 21 / 10 | |
| 0.5.67 | 21 / 10 | |
| 0.5.66 | 21 / 10 | |
| 0.5.65 | 21 / 10 | |
| 0.5.64 | 21 / 10 | |
| 0.5.63 | 21 / 10 | |
| 0.5.62 | 21 / 10 | |
| 0.5.61 | 21 / 10 | |
| 0.5.60 | 21 / 10 | |
| 0.5.59 | 21 / 10 | |
| 0.5.58 | 21 / 10 | |
| 0.5.57 | 21 / 10 | |
| 0.5.56 | 21 / 10 | |
| 0.5.55 | 21 / 10 | |
| 0.5.54 | 21 / 10 | |
| 0.5.53 | 21 / 10 | |
| 0.5.52 | 21 / 10 | |
| 0.5.51 | 21 / 10 | |
| 0.5.50 | 21 / 10 | |
| 0.5.49 | 21 / 10 | |
| 0.5.48 | 21 / 10 | |
| 0.5.47 | 21 / 10 | |
| 0.5.46 | 21 / 10 | |
| 0.5.45 | 21 / 10 | |
| 0.5.44 | 21 / 10 | |
| 0.5.43 | 21 / 10 | |
| 0.5.42 | 21 / 10 | |
| 0.5.41 | 21 / 10 |
v0.5.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.42
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 2024-02-14, 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.5.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.