ohmyfetch
oh-my-fetch
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): ohmyfetch/pi0 has a long established track record; lack of Sigstore attestation is not a disqualifier for this well-known package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): node-fetch-native is a unjs/pi0 package replacing node-fetch; this is a deliberate, expected dependency swap by the same trusted author, not a suspicious addition. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): ohmyfetch legitimately started at 0.0.0 as its initial release; it is a well-established Nuxt ecosystem package with 34k weekly downloads and 42 versions. Not a throwaway package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link dump reflects legitimate ecosystem cross-linking common in Nuxt/UnJS packages. Package is established with real usage and a trusted publisher. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.4.21 | 4 / 13 | |
| 0.4.20 | 4 / 13 | |
| 0.4.19 | 4 / 13 | |
| 0.4.17 | 4 / 14 | |
| 0.4.15 | 4 / 16 | |
| 0.4.14 | 4 / 16 | |
| 0.4.13 | 4 / 16 | |
| 0.4.12 | 4 / 16 | |
| 0.4.11 | 4 / 16 | |
| 0.4.10 | 4 / 15 | |
| 0.4.9 | 4 / 15 | |
| 0.4.8 | 4 / 14 | |
| 0.4.7 | 4 / 14 | |
| 0.4.6 | 4 / 14 | |
| 0.4.5 | 4 / 14 | |
| 0.4.4 | 4 / 14 | |
| 0.4.3 | 4 / 14 | |
| 0.4.2 | 3 / 14 | |
| 0.4.1 | 3 / 14 | |
| 0.4.0 | 3 / 14 | |
| 0.3.2 | 3 / 14 | |
| 0.3.1 | 3 / 14 | |
| 0.3.0 | 3 / 14 | |
| 0.2.0 | 3 / 14 | |
| 0.1.8 | 1 / 16 | |
| 0.1.7 | 1 / 16 | |
| 0.1.6 | 1 / 16 | |
| 0.1.5 | 1 / 16 | |
| 0.1.4 | 1 / 16 | |
| 0.1.3 | 1 / 16 | |
| 0.1.1 | 1 / 16 | |
| 0.1.0 | 1 / 16 | |
| 0.0.7 | 1 / 16 | |
| 0.0.6 | 1 / 16 | |
| 0.0.5 | 1 / 16 | |
| 0.0.4 | 1 / 16 | |
| 0.0.3 | 1 / 16 | |
| 0.0.2 | 3 / 14 | |
| 0.0.1 | 3 / 14 | |
| 0.0.0 | 3 / 14 |
v0.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
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: pi0.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
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: pi0.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
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: pi0.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.