oboe
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:http-https | AI (dependencies): http-https is a well-known, benign utility for transparent http/https routing; a natural and legitimate dependency for a streaming HTTP JSON library like oboe. | ai | |
| phantom-deps | phantom-dep:http-https | AI (phantom-deps): http-https is used in oboe's Node.js streaming HTTP implementation; the phantom-dep scanner likely misses the indirect import path. Stable false positive for this package. | ai |
v2.1.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jimhigson) than the most recent previously approved version (juancaicedo) on 2024-09-25, but jimhigson 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.