@tinyhttp/send
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tinyhttp/etag | AI (dependencies): First-party sibling dep from the tinyhttp monorepo; same publisher and trust context. | ai | |
| dependencies | unvetted-dep:@tinyhttp/content-type | AI (dependencies): First-party sibling dep from the tinyhttp monorepo; same publisher and trust context. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.8 | 4 / 0 | |
| 2.2.7 | 4 / 0 | |
| 2.2.6 | 3 / 0 | |
| 2.2.5 | 3 / 0 | |
| 2.2.4 | 3 / 0 | |
| 2.2.3 | 3 / 0 | |
| 2.2.2 | 3 / 0 |
v2.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.