← Home

@pionjs/pion

npm Repository Homepage
16
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

megheaiulian

Keywords

hauntedlitweb-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pino AI (typosquat): Scoped web-components hooks package; name similarity to pino is coincidental, not impersonation. ai

Versions (showing 16 of 16)

Version Deps Published
2.16.1 1 / 10
2.16.0 1 / 10
2.15.0 1 / 10
2.14.0 1 / 10
2.13.0 1 / 10
2.12.0 1 / 18
2.11.0 1 / 18
2.10.0 1 / 18
2.9.0 1 / 18
2.8.3 1 / 18
2.8.2 1 / 18
2.8.1 1 / 18
2.8.0 1 / 18
2.7.1 1 / 18
2.7.0 1 / 18
2.6.0 1 / 18

v2.16.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.

v2.8.2

1 finding
LOW No provenance attestation provenance

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

v2.8.1

1 finding
LOW No provenance attestation provenance

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

v2.8.0

1 finding
LOW No provenance attestation provenance

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

v2.7.1

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.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.