@pmndrs/handle
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions publishing with SLSA attestation is a legitimate CI/CD migration for the pmndrs org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-attested publish under known pmndrs org; no malicious indicators. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer added under established pmndrs org with SLSA-attested publish; consistent with org-level access management. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 6.6.30 | 2 / 0 | |
| 6.6.29 | 2 / 0 | |
| 6.6.28 | 2 / 0 | |
| 6.6.27 | 2 / 0 | |
| 6.6.26 | 2 / 0 | |
| 6.6.25 | 2 / 0 | |
| 6.6.24 | 2 / 0 | |
| 6.6.23 | 2 / 0 | |
| 6.6.22 | 2 / 0 | |
| 6.6.21 | 2 / 0 | |
| 6.6.20 | 2 / 0 | |
| 6.6.19 | 2 / 0 | |
| 6.6.18 | 2 / 0 | |
| 6.6.17 | 2 / 0 | |
| 6.6.16 | 2 / 0 | |
| 6.6.15 | 2 / 0 | |
| 6.6.14 | 2 / 0 | |
| 6.6.13 | 2 / 0 | |
| 6.6.12 | 2 / 0 | |
| 6.6.11 | 2 / 0 | |
| 6.6.10 | 2 / 0 | |
| 6.6.9 | 2 / 0 | |
| 6.6.8 | 2 / 0 | |
| 6.6.7 | 2 / 0 | |
| 6.6.6 | 2 / 0 | |
| 6.6.5 | 2 / 0 | |
| 6.6.4 | 2 / 0 | |
| 6.6.3 | 2 / 0 | |
| 6.6.2 | 2 / 0 | |
| 6.6.1 | 2 / 0 | |
| 6.6.0 | 2 / 0 | |
| 6.5.6 | 2 / 0 | |
| 6.5.5 | 2 / 0 | |
| 6.5.4 | 2 / 0 | |
| 6.5.3 | 2 / 0 | |
| 6.5.2 | 2 / 0 | |
| 6.5.1 | 2 / 0 | |
| 6.5.0 | 2 / 0 |
v6.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.