ethereumjs-util No license 17 versions

ethereumjs-util

npm Repository Homepage

17

Versions

—

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

holgerd77evertonfragaralxznull_radixaxicjwasinger

Keywords

ethereumutilitiesutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	large-new-source-files	AI (source-diff): Monorepo TS build produces many small compiled files; not injected code.	ai	2026/07/21
source-diff	source-size-tripled	AI (source-diff): Explained by added dist.browser bundle and TS build scripts.	ai	2026/07/21
publish-pattern	dormant-publish	AI (publish-pattern): Long-standing trusted publisher/package; dormancy is monorepo release cadence, not takeover.	ai	2026/07/21
provenance	missing-githead	AI (provenance): Metadata-only; publish-env change with no payload, stable for this well-known package.	ai	2026/07/21
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding in ethereumjs-util is standard Ethereum cryptographic implementation (e.g., EIP-1014 CREATE2 address derivation using 0xff prefix). These are known constants, not obfuscated payloads.	ai	2026/04/26
phantom-deps	phantom-dep:@types/bn.js	AI (phantom-deps): @types/bn.js is intentionally listed as a runtime dep to re-export TypeScript types; not a security concern for this package.	ai	2026/04/26

Versions (showing 17 of 17)

Version	Deps	Published
7.1.5	5 / 15	2022-06-03
7.1.4	5 / 15	2022-02-01
7.1.3	5 / 15	2021-10-14
7.1.2	6 / 15	2021-09-29
7.1.1	6 / 15	2021-09-27
7.1.0	6 / 16	2021-07-08
7.0.10	6 / 22	2021-04-01
7.0.9	6 / 20	2021-03-04
7.0.8	6 / 21	2021-02-02
7.0.7	6 / 21	2020-10-19
7.0.6	6 / 21	2020-10-08
7.0.5	6 / 21	2020-09-10
7.0.4	6 / 21	2020-08-04
7.0.3	6 / 21	2020-07-08
7.0.2	7 / 21	2020-05-26
7.0.1	7 / 21	2020-05-15
7.0.0	7 / 21	2020-04-30

v7.1.4

1 finding

LOW No provenance attestation provenance

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

v7.1.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: holgerd77.

LOW No provenance attestation provenance

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

v7.1.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: holgerd77.

LOW No provenance attestation provenance

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

v7.1.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: holgerd77.

LOW No provenance attestation provenance

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

v7.1.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: holgerd77.

LOW No provenance attestation provenance

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

v7.0.10

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: holgerd77.

LOW No provenance attestation provenance

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

v7.0.9

1 finding

LOW No provenance attestation provenance

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

v7.0.8

1 finding

LOW No provenance attestation provenance

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

v7.0.7

1 finding

LOW No provenance attestation provenance

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

v7.0.6

1 finding

LOW No provenance attestation provenance

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

v7.0.5

1 finding

LOW No provenance attestation provenance

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

v7.0.4

1 finding

LOW No provenance attestation provenance

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

v7.0.3

1 finding

LOW No provenance attestation provenance

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

v7.0.2

1 finding

LOW No provenance attestation provenance

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

v7.0.1

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.

v7.0.0

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.