← Home

@remix-project/remix-lib

npm Repository Homepage

Library to various Remix tools

100
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ryestewyann300aniket-enggioedeveloperyann_remixlabs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Publisher is long-tenured known maintainer of the Remix project. ai
phantom-deps phantom-dep:@ethereumjs/vm AI (phantom-deps): Legit ethereum tooling dep, likely used via re-export/build; stable across versions. ai
provenance publisher-changed-stale AI (provenance): Old publisher change (2021), long stable availability, established maintainer track record. ai
phantom-deps phantom-dep:@ethereumjs/blockchain AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. ai
semgrep semgrep:hex-decode AI (semgrep): Buffer.from(hex) used for EVM transaction encoding — standard pattern in this Ethereum tooling library. ai
phantom-deps phantom-dep:@ethereumjs/statemanager AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. ai
phantom-deps phantom-dep:events AI (phantom-deps): Common polyfill dep in Ethereum monorepo; stable false positive for this package. ai
phantom-deps phantom-dep:@ethereumjs/mpt AI (phantom-deps): EthereumJS monorepo peer dep; stable false positive for this package. ai

Versions (showing 100 of 106)

Version Deps Published
0.5.101 21 / 9
0.5.100 21 / 9
0.5.99 21 / 9
0.5.98 21 / 9
0.5.97 19 / 9
0.5.96 13 / 9
0.5.95 13 / 9
0.5.94 13 / 9
0.5.93 13 / 9
0.5.92 13 / 9
0.5.91 13 / 9
0.5.90 13 / 9
0.5.89 13 / 9
0.5.88 13 / 9
0.5.87 15 / 9
0.5.86 15 / 9
0.5.85 15 / 9
0.5.84 15 / 9
0.5.83 15 / 9
0.5.82 15 / 9
0.5.81 15 / 9
0.5.80 15 / 9
0.5.79 15 / 9
0.5.78 15 / 9
0.5.77 14 / 9
0.5.76 14 / 9
0.5.75 14 / 9
0.5.74 13 / 9
0.5.73 12 / 9
0.5.72 12 / 9
0.5.71 12 / 9
0.5.70 12 / 9
0.5.69 12 / 9
0.5.68 12 / 9
0.5.67 12 / 9
0.5.66 12 / 9
0.5.65 12 / 9
0.5.64 12 / 9
0.5.63 12 / 9
0.5.62 12 / 9
0.5.61 12 / 9
0.5.60 12 / 9
0.5.59 12 / 9
0.5.58 12 / 9
0.5.57 12 / 9
0.5.56 12 / 9
0.5.55 12 / 9
0.5.54 12 / 9
0.5.53 12 / 9
0.5.52 12 / 9
0.5.51 12 / 9
0.5.50 12 / 9
0.5.49 12 / 9
0.5.48 12 / 9
0.5.47 12 / 9
0.5.46 12 / 9
0.5.45 12 / 9
0.5.44 12 / 9
0.5.43 12 / 9
0.5.42 11 / 9
0.5.41 10 / 9
0.5.40 9 / 9
0.5.39 9 / 9
0.5.38 9 / 9
0.5.37 9 / 9
0.5.36 9 / 9
0.5.35 9 / 9
0.5.34 9 / 9
0.5.33 9 / 9
0.5.32 9 / 9
0.5.30 8 / 9
0.5.29 8 / 9
0.5.28 8 / 9
0.5.27 8 / 9
0.5.26 8 / 9
0.5.25 8 / 9
0.5.24 8 / 9
0.5.23 8 / 9
0.5.22 8 / 9
0.5.21 11 / 9
0.5.20 11 / 9
0.5.19 11 / 9
0.5.18 11 / 9
0.5.17 11 / 9
0.5.16 11 / 9
0.5.15 11 / 9
0.5.14 11 / 9
0.5.13 11 / 9
0.5.12 11 / 9
0.5.11 11 / 9
0.5.10 11 / 9
0.5.9 11 / 9
0.5.8 10 / 9
0.5.7 10 / 9
0.5.6 10 / 9
0.5.5 10 / 9
0.5.4 10 / 9
0.5.3 10 / 9
0.5.2 9 / 9
0.5.1 9 / 9
Showing 100 of 106 Next page →

v0.5.101

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → yann_remixlabs (on 2026-06-06, known maintainer) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.5.94

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → yann_remixlabs (on 2026-03-27, known maintainer) provenance

This version was published by a different npm account (yann_remixlabs) than the most recent previously approved version (aniket-engg) on 2026-03-27, 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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.72

1 finding
LOW No provenance attestation provenance

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

v0.5.71

1 finding
LOW No provenance attestation provenance

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

v0.5.70

1 finding
LOW No provenance attestation provenance

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

v0.5.69

1 finding
LOW No provenance attestation provenance

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

v0.5.68

1 finding
LOW No provenance attestation provenance

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

v0.5.67

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.54

1 finding
LOW No provenance attestation provenance

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

v0.5.53

1 finding
LOW No provenance attestation provenance

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

v0.5.52

1 finding
LOW No provenance attestation provenance

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

v0.5.51

1 finding
LOW No provenance attestation provenance

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

v0.5.50

1 finding
LOW No provenance attestation provenance

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

v0.5.49

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → yann300 (on 2024-02-14, known maintainer) provenance

This version was published by a different npm account (yann300) than the most recent previously approved version (aniket-engg) on 2024-02-14, but yann300 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.5.48

1 finding
LOW No provenance attestation provenance

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

v0.5.47

1 finding
LOW No provenance attestation provenance

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

v0.5.46

1 finding
LOW No provenance attestation provenance

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

v0.5.45

1 finding
LOW No provenance attestation provenance

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

v0.5.44

1 finding
LOW No provenance attestation provenance

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

v0.5.43

1 finding
LOW No provenance attestation provenance

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

v0.5.42

1 finding
LOW No provenance attestation provenance

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

v0.5.41

1 finding
LOW No provenance attestation provenance

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

v0.5.40

1 finding
LOW No provenance attestation provenance

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

v0.5.39

1 finding
LOW No provenance attestation provenance

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

v0.5.38

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yann300 → aniket-engg (on 2023-08-16, known maintainer) provenance

This version was published by a different npm account (aniket-engg) than the most recent previously approved version (yann300) on 2023-08-16, but aniket-engg 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.5.37

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yann300 → aniket-engg (on 2023-07-17, known maintainer) provenance

This version was published by a different npm account (aniket-engg) than the most recent previously approved version (yann300) on 2023-07-17, but aniket-engg 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.5.36

1 finding
LOW No provenance attestation provenance

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

v0.5.35

1 finding
LOW No provenance attestation provenance

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

v0.5.34

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ioedeveloper → yann300 (on 2023-06-29, known maintainer) provenance

This version was published by a different npm account (yann300) than the most recent previously approved version (ioedeveloper) on 2023-06-29, but yann300 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.5.33

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ioedeveloper → yann300 (on 2023-06-29, known maintainer) provenance

This version was published by a different npm account (yann300) than the most recent previously approved version (ioedeveloper) on 2023-06-29, but yann300 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.5.32

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → ioedeveloper (on 2023-05-11, known maintainer) provenance

This version was published by a different npm account (ioedeveloper) than the most recent previously approved version (aniket-engg) on 2023-05-11, but ioedeveloper 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.5.30

1 finding
LOW No provenance attestation provenance

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

v0.5.29

1 finding
LOW No provenance attestation provenance

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

v0.5.28

1 finding
LOW No provenance attestation provenance

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

v0.5.27

1 finding
LOW No provenance attestation provenance

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

v0.5.26

1 finding
LOW No provenance attestation provenance

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

v0.5.25

1 finding
LOW No provenance attestation provenance

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

v0.5.24

1 finding
LOW No provenance attestation provenance

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

v0.5.23

1 finding
LOW No provenance attestation provenance

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

v0.5.22

1 finding
LOW No provenance attestation provenance

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

v0.5.21

1 finding
LOW No provenance attestation provenance

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

v0.5.20

1 finding
LOW No provenance attestation provenance

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

v0.5.19

1 finding
LOW No provenance attestation provenance

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

v0.5.18

1 finding
LOW No provenance attestation provenance

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

v0.5.17

1 finding
LOW No provenance attestation provenance

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

v0.5.16

1 finding
LOW No provenance attestation provenance

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

v0.5.15

1 finding
LOW No provenance attestation provenance

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

v0.5.14

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → yann300 (on 2022-06-06, known maintainer) provenance

This version was published by a different npm account (yann300) than the most recent previously approved version (aniket-engg) on 2022-06-06, but yann300 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.5.13

1 finding
LOW No provenance attestation provenance

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

v0.5.12

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → yann300 (on 2022-04-14, known maintainer) provenance

This version was published by a different npm account (yann300) than the most recent previously approved version (aniket-engg) on 2022-04-14, but yann300 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.5.11

1 finding
LOW No provenance attestation provenance

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

v0.5.10

1 finding
LOW No provenance attestation provenance

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

v0.5.9

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → ioedeveloper (on 2021-11-23, known maintainer) provenance

This version was published by a different npm account (ioedeveloper) than the most recent previously approved version (aniket-engg) on 2021-11-23, but ioedeveloper 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.5.8

1 finding
LOW No provenance attestation provenance

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

v0.5.7

2 findings
MEDIUM Publisher changed: aniket-engg → ryestew (on 2021-09-15, unremoved on npm for 1773d) provenance

This version was published by a different npm account (ryestew) than the most recent previously approved version (aniket-engg) on 2021-09-15. It has since remained available on npm for 1773 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.5.6

1 finding
LOW No provenance attestation provenance

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

v0.5.5

1 finding
LOW No provenance attestation provenance

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

v0.5.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → ioedeveloper (on 2021-07-28, known maintainer) provenance

This version was published by a different npm account (ioedeveloper) than the most recent previously approved version (aniket-engg) on 2021-07-28, but ioedeveloper 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.5.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ioedeveloper → aniket-engg (on 2021-07-08, known maintainer) provenance

This version was published by a different npm account (aniket-engg) than the most recent previously approved version (ioedeveloper) on 2021-07-08, but aniket-engg 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.5.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ioedeveloper → aniket-engg (on 2021-06-24, known maintainer) provenance

This version was published by a different npm account (aniket-engg) than the most recent previously approved version (ioedeveloper) on 2021-06-24, but aniket-engg 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.5.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aniket-engg → ioedeveloper (on 2021-06-23, known maintainer) provenance

This version was published by a different npm account (ioedeveloper) than the most recent previously approved version (aniket-engg) on 2021-06-23, but ioedeveloper 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.