@eth-optimism/core-utils
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:bufio | AI (dependencies): Standard buffer utility lib used alongside ethersproject packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Diff baseline is stale; monorepo has continuously published since, not dormant. | ai | |
| phantom-deps | phantom-dep:@ethersproject/web | AI (phantom-deps): Used transitively/config-only; benign for this ethers-based utils package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer roster churn in long-lived monorepo, no takeover indicators. | ai | |
| phantom-deps | phantom-dep:@types/pino-multi-stream | AI (phantom-deps): Type-only package loaded by convention; stable FP. | ai | |
| provenance | missing-githead | AI (provenance): Publish-env change on trusted first-party Optimism package; not a compromise indicator here. | ai | |
| phantom-deps | phantom-dep:ethers | AI (phantom-deps): Core dep referenced across builds; stable FP. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Utility dep; stable FP. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Logger used via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@ethersproject/abstract-provider | AI (phantom-deps): Config-only usage, stable false positive. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Config-only usage, stable false positive. | ai | |
| phantom-deps | phantom-dep:colors | AI (phantom-deps): Config-only usage, stable false positive. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): Config-only usage, stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Established Optimism monorepo package predating Sigstore provenance; absence is expected and not a risk signal for this package. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 14 / 2 | |
| 0.12.2 | 14 / 2 | |
| 0.12.1 | 12 / 2 | |
| 0.12.0 | 16 / 1 | |
| 0.9.3 | 8 / 1 | |
| 0.8.3 | 8 / 19 | |
| 0.8.0 | 6 / 19 | |
| 0.7.7 | 7 / 20 | |
| 0.7.6 | 7 / 20 | |
| 0.7.5 | 7 / 20 | |
| 0.7.4 | 7 / 20 | |
| 0.7.3 | 7 / 21 | |
| 0.7.2 | 7 / 21 | |
| 0.7.1 | 7 / 21 | |
| 0.7.0 | 7 / 21 | |
| 0.6.1 | 4 / 23 | |
| 0.6.0 | 4 / 23 | |
| 0.5.5 | 3 / 23 | |
| 0.5.4 | 3 / 22 | |
| 0.5.3 | 3 / 22 | |
| 0.5.2 | 3 / 22 | |
| 0.5.1 | 3 / 22 | |
| 0.5.0 | 3 / 22 | |
| 0.4.7 | 3 / 19 | |
| 0.4.6 | 3 / 19 | |
| 0.4.5 | 3 / 13 | |
| 0.4.4 | 3 / 13 | |
| 0.4.3 | 3 / 13 | |
| 0.4.2 | 3 / 13 | |
| 0.4.1 | 3 / 9 | |
| 0.4.0 | 3 / 9 | |
| 0.3.2 | 9 / 10 | |
| 0.3.1 | 9 / 10 | |
| 0.3.0 | 9 / 10 | |
| 0.2.3 | 4 / 10 | |
| 0.2.2 | 4 / 10 | |
| 0.2.1 | 4 / 10 | |
| 0.2.0 | 4 / 10 | |
| 0.1.10 | 5 / 5 | |
| 0.1.9 | 6 / 5 | |
| 0.1.8 | 4 / 4 | |
| 0.1.7 | 4 / 4 | |
| 0.1.6 | 3 / 4 | |
| 0.1.5 | 9 / 13 | |
| 0.1.4 | 9 / 13 | |
| 0.1.3 | 9 / 13 | |
| 0.1.2 | 9 / 13 | |
| 0.1.1 | 9 / 13 | |
| 0.1.0 | 9 / 13 |
v0.12.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: optibot.
This version was published by a different npm account (optibot) than the most recent previously approved version (karlfloersch) on 2023-07-20. It has since remained available on npm for 1095 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
2 findingsThis version was published by a different npm account (optibot) than the most recent previously approved version (karlfloersch) on 2023-06-20. It has since remained available on npm for 1125 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: karlfloersch.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
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 (karlfloersch) than the most recent previously approved version (tynes) on 2021-02-24, but karlfloersch 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.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.