@jsdevtools/ono
Throw better errors.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pino | AI (typosquat): @jsdevtools/ono is a legitimate, long-established error-handling utility with no relation to pino (a logger). The name similarity is purely coincidental; scoped package under a known org. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.1.3 | 0 / 15 | |
| 7.1.2 | 0 / 18 | |
| 7.1.1 | 0 / 18 | |
| 7.1.0 | 0 / 18 | |
| 7.0.1 | 0 / 18 | |
| 7.0.0 | 0 / 18 | |
| 6.0.1 | 0 / 18 |
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.