@remix-project/remix-analyzer
Tool to perform static analysis on Solidity smart contracts
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@ethereumjs/tx | AI (npm-metadata): Remix team's own fork used as a temporary compatibility fix; consistent with project's known development patterns. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fast-levenshtein is a well-known benign utility; appropriate for a static analysis tool doing similarity checks. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Remix Project package with 122 versions; dormancy reflects monorepo release cadence, not account takeover. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/tx | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/vm | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/block | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:string-similarity | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@ethereumjs/util | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:ethjs-util | AI (phantom-deps): Config-file reference only; stable false positive for this monorepo package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.5.100 | 11 / 8 | |
| 0.5.99 | 11 / 8 | |
| 0.5.98 | 11 / 8 | |
| 0.5.97 | 11 / 8 | |
| 0.5.96 | 10 / 8 | |
| 0.5.95 | 10 / 8 | |
| 0.5.94 | 10 / 8 | |
| 0.5.93 | 10 / 8 | |
| 0.5.92 | 10 / 8 | |
| 0.5.91 | 10 / 8 | |
| 0.5.90 | 10 / 8 | |
| 0.5.89 | 11 / 8 | |
| 0.5.88 | 11 / 8 | |
| 0.5.87 | 11 / 8 | |
| 0.5.86 | 11 / 8 | |
| 0.5.85 | 11 / 8 | |
| 0.5.84 | 11 / 8 | |
| 0.5.83 | 11 / 8 | |
| 0.5.82 | 11 / 8 | |
| 0.5.81 | 11 / 8 | |
| 0.5.80 | 11 / 8 | |
| 0.5.79 | 11 / 8 | |
| 0.5.78 | 11 / 8 |
v0.5.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.