@learncard/vpqr-plugin
[<img src="https://user-images.githubusercontent.com/2185016/190510561-294db809-09fd-4771-9749-6c0e0f4144fd.png" width="215"/>](https://learncard.com)
Supply chain provenance
Status for the latest visible version.
Maintainers
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 publisher is consistent with CI/CD automation; SLSA attestation confirms supply chain integrity. | ai | |
| phantom-deps | phantom-dep:@digitalbazaar/vpqr | AI (phantom-deps): Declared as runtime dep; may be used indirectly via bundled dist rather than direct import. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo plugin with docs-heavy README; link dump is documentation, not phishing. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 1.1.27 | 3 / 9 | |
| 1.1.26 | 3 / 9 | |
| 1.1.25 | 3 / 9 | |
| 1.1.24 | 3 / 9 | |
| 1.1.23 | 3 / 9 | |
| 1.1.22 | 3 / 9 | |
| 1.1.21 | 3 / 9 | |
| 1.1.20 | 3 / 9 | |
| 1.1.19 | 3 / 9 | |
| 1.1.18 | 3 / 9 | |
| 1.1.17 | 3 / 9 | |
| 1.1.16 | 3 / 9 | |
| 1.1.14 | 3 / 9 | |
| 1.1.13 | 3 / 9 | |
| 1.1.12 | 3 / 9 | |
| 1.1.9 | 3 / 9 | |
| 1.1.8 | 3 / 9 | |
| 1.1.7 | 3 / 9 | |
| 1.1.6 | 3 / 9 | |
| 1.1.4 | 3 / 9 | |
| 1.1.2 | 3 / 9 | |
| 1.1.1 | 3 / 9 | |
| 1.0.55 | 3 / 9 | |
| 1.0.54 | 3 / 9 | |
| 1.0.53 | 3 / 9 | |
| 1.0.52 | 3 / 9 | |
| 1.0.51 | 3 / 9 | |
| 1.0.50 | 3 / 9 | |
| 1.0.49 | 3 / 9 | |
| 1.0.48 | 3 / 9 | |
| 1.0.47 | 3 / 9 | |
| 1.0.46 | 3 / 9 | |
| 1.0.44 | 3 / 9 | |
| 1.0.43 | 3 / 9 | |
| 1.0.42 | 3 / 9 | |
| 1.0.41 | 3 / 9 | |
| 1.0.40 | 3 / 9 | |
| 1.0.39 | 3 / 9 | |
| 1.0.38 | 3 / 9 | |
| 1.0.37 | 3 / 9 | |
| 1.0.36 | 3 / 9 | |
| 1.0.35 | 3 / 9 | |
| 1.0.34 | 3 / 9 | |
| 1.0.33 | 3 / 9 | |
| 1.0.32 | 3 / 9 | |
| 1.0.31 | 3 / 9 | |
| 1.0.30 | 3 / 9 | |
| 1.0.29 | 3 / 9 | |
| 1.0.28 | 3 / 9 | |
| 1.0.27 | 3 / 9 | |
| 1.0.26 | 3 / 9 | |
| 1.0.25 | 3 / 9 | |
| 1.0.24 | 3 / 9 | |
| 1.0.23 | 3 / 9 | |
| 1.0.22 | 3 / 9 | |
| 1.0.21 | 3 / 9 | |
| 1.0.20 | 3 / 9 | |
| 1.0.19 | 3 / 9 | |
| 1.0.18 | 3 / 9 | |
| 1.0.17 | 3 / 9 | |
| 1.0.16 | 3 / 9 | |
| 1.0.15 | 3 / 9 | |
| 1.0.14 | 3 / 9 | |
| 1.0.13 | 3 / 9 | |
| 1.0.12 | 3 / 9 | |
| 1.0.11 | 3 / 9 | |
| 1.0.10 | 3 / 9 |
v1.1.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.