@remix-project/remixd
remix server: allow accessing file system from remix.ethereum.org and start a dev environment (see help section)
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher is a known maintainer on prior approved versions; not indicative of account takeover. | ai | |
| phantom-deps | phantom-dep:bn.js | AI (phantom-deps): Config-file reference in established package; stable pattern. | ai | |
| dependencies | unvetted-dep:@remixproject/plugin | AI (dependencies): First-party sibling package from the same remixproject org; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@remixproject/plugin-ws | AI (dependencies): First-party sibling package from the same remixproject org; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in installSlither.js dev tool script, not in install hooks or runtime attack surface. | ai | |
| phantom-deps | phantom-dep:@remix-project/remix-solidity | AI (phantom-deps): Same-org package; phantom-dep heuristic unreliable for monorepo siblings. | ai | |
| phantom-deps | phantom-dep:@remixproject/plugin-api | AI (phantom-deps): Same-org plugin package; referenced via config/type re-exports, stable false positive. | ai | |
| phantom-deps | phantom-dep:@remixproject/plugin-utils | AI (phantom-deps): Same-org plugin package; referenced via config/type re-exports, stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.6.65 | 14 / 15 | |
| 0.6.64 | 14 / 15 | |
| 0.6.63 | 14 / 15 | |
| 0.6.62 | 14 / 15 | |
| 0.6.61 | 14 / 15 | |
| 0.6.60 | 14 / 15 | |
| 0.6.57 | 14 / 15 | |
| 0.6.47 | 13 / 15 |
v0.6.65
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 (yann_remixlabs) than the most recent previously approved version (aniket-engg) on 2026-06-06, but yann_remixlabs 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.6.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.