@remix-project/remix-simulator MIT 23 versions

@remix-project/remix-simulator

npm Repository Homepage

Ethereum IDE and tools for the web

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 owned by yann300 (listed Remix contributor); appears to be a temporary v10 compatibility patch within the trusted project org.	ai	2026/05/04
phantom-deps	phantom-dep:rlp	AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:async	AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:commander	AI (phantom-deps): Declared dep used by bin/ethsim CLI entry; heuristic false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:ethjs-util	AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:string-similarity	AI (phantom-deps): Declared dep in a multi-lib monorepo; heuristic false positive for this package.	ai	2026/04/29

Versions (showing 23 of 23)

Version	Deps	Published
0.2.91	25 / 9	2026-04-27
0.2.90	25 / 9	2026-04-15
0.2.89	25 / 9	2026-04-09
0.2.88	25 / 9	2026-04-09
0.2.87	23 / 9	2026-04-09
0.2.86	23 / 9	2026-03-27
0.2.85	23 / 9	2026-03-26
0.2.84	23 / 9	2025-12-24
0.2.83	23 / 9	2025-12-10
0.2.82	23 / 9	2025-12-03
0.2.81	23 / 9	2025-11-18
0.2.80	25 / 9	2025-10-16
0.2.79	25 / 9	2025-09-23
0.2.78	25 / 9	2025-09-09
0.2.77	25 / 9	2025-08-28
0.2.76	25 / 9	2025-08-26
0.2.75	25 / 9	2025-08-05
0.2.74	25 / 9	2025-07-15
0.2.73	25 / 9	2025-06-30
0.2.72	25 / 9	2025-05-22
0.2.71	25 / 9	2025-05-08
0.2.70	25 / 9	2025-05-08
0.2.69	25 / 9	2025-05-08

v0.2.90

1 finding

LOW No provenance attestation provenance

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

v0.2.89

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.2.88

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.2.87

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.2.86

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.2.85

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.2.84

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.2.83

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.2.82

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.2.81

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.2.80

1 finding

LOW No provenance attestation provenance

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

v0.2.79

1 finding

LOW No provenance attestation provenance

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

v0.2.78

1 finding

LOW No provenance attestation provenance

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

v0.2.77

1 finding

LOW No provenance attestation provenance

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

v0.2.76

1 finding

LOW No provenance attestation provenance

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

v0.2.75

1 finding

LOW No provenance attestation provenance

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

v0.2.74

1 finding

LOW No provenance attestation provenance

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

v0.2.73

1 finding

LOW No provenance attestation provenance

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

v0.2.72

1 finding

LOW No provenance attestation provenance

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

v0.2.71

1 finding

LOW No provenance attestation provenance

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

v0.2.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.2.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.