own-or
Either use the object's own property, or a fallback
1
Versions
ISC
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
isaacs
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): own-or is a legitimate micro-utility by npm's creator (isaacs). Tiny size and no deps are expected for this type of helper. SPAM-FLAGGED publisher signal is a false positive for this well-known maintainer. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm by many years; absence is expected and not a risk signal here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 0 |
v1.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.