@remix-project/remix-astwalker
Tool to walk through Solidity AST
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
Keywords
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): Remix Project uses a fork of ethereumjs-vm; GitHub URL dep is a known pattern for this monorepo across many versions. | ai | |
| phantom-deps | phantom-dep:tape | AI (phantom-deps): Test framework declared as dep in monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): Utility declared as dep; monorepo workspace pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Declared dep used transitively in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): Build/test tool in monorepo workspace; stable false positive. | ai | |
| phantom-deps | phantom-dep:ethjs-util | AI (phantom-deps): Declared dep in monorepo workspace; stable false positive. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build tool declared as dep in monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:nyc | AI (phantom-deps): Monorepo workspace dev tool declared as dep; not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/tx | AI (phantom-deps): Declared dep in monorepo workspace; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/vm | AI (phantom-deps): Declared dep in monorepo workspace; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/util | AI (phantom-deps): Declared dep in monorepo workspace; stable false positive. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/block | AI (phantom-deps): Declared dep in monorepo workspace; stable false positive. | ai | |
| phantom-deps | phantom-dep:string-similarity | AI (phantom-deps): Declared dep in monorepo workspace; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/tape | AI (phantom-deps): Type definitions for test framework; stable false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.0.121 | 14 / 1 | |
| 0.0.120 | 14 / 1 | |
| 0.0.119 | 14 / 1 | |
| 0.0.118 | 14 / 1 | |
| 0.0.117 | 14 / 1 | |
| 0.0.116 | 14 / 1 | |
| 0.0.115 | 14 / 1 | |
| 0.0.114 | 14 / 1 | |
| 0.0.113 | 14 / 1 | |
| 0.0.112 | 14 / 1 | |
| 0.0.111 | 14 / 1 | |
| 0.0.110 | 15 / 1 | |
| 0.0.109 | 15 / 1 | |
| 0.0.108 | 15 / 1 | |
| 0.0.107 | 15 / 1 | |
| 0.0.106 | 15 / 1 | |
| 0.0.105 | 15 / 1 | |
| 0.0.104 | 15 / 1 | |
| 0.0.103 | 15 / 1 | |
| 0.0.102 | 15 / 1 | |
| 0.0.101 | 15 / 1 | |
| 0.0.100 | 15 / 1 | |
| 0.0.99 | 15 / 1 |
v0.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.