← Home

bare-pipe

npm Repository Homepage

Native I/O pipes for JavaScript

18
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mafintosh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Holepunchto org publishes via GitHub Actions CI/CD with SLSA attestation; machine publisher is expected for this package. ai
maintainer-change maintainer-removed AI (maintainer-change): Transition to GitHub Actions CI/CD publishing is consistent with org-level automation; not indicative of takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI/CD-attested publish from the same org repo is low risk for this package. ai
npm-metadata bundled-binaries AI (npm-metadata): Holepunch native addon; prebuilt .bare binaries for multiple platforms are the documented distribution mechanism. ai

Versions (showing 18 of 18)

Version Deps Published
4.2.3 2 / 7
4.2.2 2 / 7
4.2.1 2 / 7
4.2.0 2 / 7
4.1.5 2 / 5
4.1.4 2 / 5
4.1.3 2 / 5
4.1.2 2 / 5
4.1.1 2 / 5
4.1.0 2 / 5
4.0.7 2 / 5
4.0.6 2 / 5
4.0.5 2 / 5
4.0.4 2 / 5
4.0.3 2 / 5
4.0.2 2 / 5
4.0.1 2 / 5
4.0.0 2 / 5

v4.2.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.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.