@remix-project/remix-url-resolver
Solidity import url resolver engine
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; no code changes from prior release. | ai | |
| dependencies | unvetted-dep:@erebos/bzz-node | AI (dependencies): @erebos/bzz-node is a legitimate Swarm client library; its use is consistent with this URL resolver's decentralized storage support. | ai | |
| provenance | no-provenance | AI (provenance): Long-established Remix monorepo package; lack of provenance is consistent across its 135 published versions. | ai | |
| phantom-deps | phantom-dep:url | AI (phantom-deps): url is a declared runtime dep used transitively; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:valid-url | AI (phantom-deps): valid-url is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.0.123 | 5 / 9 | |
| 0.0.122 | 5 / 9 | |
| 0.0.121 | 5 / 9 | |
| 0.0.120 | 5 / 9 | |
| 0.0.119 | 5 / 9 | |
| 0.0.118 | 5 / 9 | |
| 0.0.117 | 5 / 9 | |
| 0.0.116 | 5 / 9 | |
| 0.0.114 | 5 / 9 | |
| 0.0.113 | 5 / 9 | |
| 0.0.112 | 5 / 9 | |
| 0.0.110 | 5 / 9 | |
| 0.0.107 | 5 / 9 | |
| 0.0.106 | 5 / 9 | |
| 0.0.104 | 5 / 9 | |
| 0.0.102 | 5 / 9 | |
| 0.0.98 | 5 / 9 |
v0.0.123
2 findings[Accepted risk] Package 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.0.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.