@remix-project/remix-solidity MIT 23 versions

@remix-project/remix-solidity

npm Repository Homepage

Tool to load and run Solidity compiler

23

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ryestewyann300aniket-enggioedeveloperyann_remixlabs

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 by yann300 (Remix core contributor); consistent with Remix project's development pattern for upstream fixes.	ai	2026/05/04
phantom-deps	phantom-dep:ethers	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:minixhr	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:ethjs-util	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-scope	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@ethereumjs/tx	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:async	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@ethereumjs/util	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@ethereumjs/block	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:string-similarity	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:webworkify-webpack	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@remix-project/remix-lib	AI (phantom-deps): Same-org sibling dep; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@ethereumjs/vm	AI (phantom-deps): Monorepo build config artifact; stable false positive for this package.	ai	2026/04/29

Versions (showing 23 of 23)

Version	Deps	Published
0.5.77	14 / 10	2026-04-27
0.5.76	14 / 10	2026-04-15
0.5.75	14 / 10	2026-04-09
0.5.74	14 / 10	2026-04-09
0.5.73	14 / 10	2026-04-09
0.5.72	14 / 10	2026-03-27
0.5.71	14 / 10	2026-03-26
0.5.70	14 / 10	2025-12-24
0.5.69	14 / 10	2025-12-10
0.5.68	14 / 10	2025-12-03
0.5.67	14 / 10	2025-11-18
0.5.66	15 / 10	2025-10-16
0.5.65	15 / 10	2025-09-23
0.5.64	15 / 10	2025-09-09
0.5.63	15 / 10	2025-08-28
0.5.62	15 / 10	2025-08-26
0.5.61	15 / 10	2025-08-05
0.5.60	15 / 10	2025-07-15
0.5.59	15 / 10	2025-06-30
0.5.58	15 / 10	2025-05-22
0.5.57	15 / 10	2025-05-08
0.5.56	15 / 10	2025-05-08
0.5.55	15 / 10	2025-05-08

v0.5.76

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.75

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.74

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.73

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.72

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.71

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.70

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.69

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.68

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.67

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.66

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.65

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.64

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.63

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.62

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.61

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.60

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.59

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.58

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.57

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.56

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.55

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.