← Home

bare-process

12
Versions
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
dependencies unvetted-dep:bare-env AI (dependencies): Same-org bare-* ecosystem dep; stable pattern for this package family. ai
dependencies unvetted-dep:bare-abort AI (dependencies): Same-org bare-* ecosystem dep; stable pattern for this package family. ai
dependencies unvetted-dep:bare-stdio AI (dependencies): Same-org bare-* ecosystem dep; stable pattern for this package family. ai
dependencies unvetted-dep:bare-signals AI (dependencies): Same-org bare-* ecosystem dep; stable pattern for this package family. ai

Versions (showing 12 of 12)

Version Deps Published
4.5.1 8 / 4
4.5.0 8 / 4
4.4.1 7 / 4
4.4.0 8 / 3
4.3.0 8 / 3
4.2.2 7 / 3
4.2.1 7 / 3
4.2.0 7 / 3
4.1.2 7 / 3
4.1.1 7 / 3
4.1.0 7 / 3
4.0.0 7 / 3

v4.5.1

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

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

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.