@learncard/chapi-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 CI/CD publisher is confirmed by SLSA provenance attestation; stable pattern for this org going forward. | ai | |
| dependencies | unvetted-dep:web-credential-handler | AI (dependencies): Expected runtime dep for a CHAPI plugin; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:credential-handler-polyfill | AI (dependencies): Expected runtime dep for a CHAPI plugin; stable across versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate monorepo plugin from Learning Economy Foundation; README links are docs references, not a phishing link farm. | ai | |
| phantom-deps | phantom-dep:web-credential-handler | AI (phantom-deps): CHAPI plugin; dependency is referenced in config/build rather than direct import — expected for this plugin type. | ai | |
| phantom-deps | phantom-dep:credential-handler-polyfill | AI (phantom-deps): Polyfill loaded via config/build pipeline, not direct import — stable pattern for this package. | ai |
Versions (showing 80 of 80)
| Version | Deps | Published |
|---|---|---|
| 1.1.27 | 4 / 10 | |
| 1.1.26 | 4 / 10 | |
| 1.1.25 | 4 / 10 | |
| 1.1.24 | 4 / 10 | |
| 1.1.23 | 4 / 10 | |
| 1.1.22 | 4 / 10 | |
| 1.1.21 | 4 / 10 | |
| 1.1.20 | 4 / 10 | |
| 1.1.19 | 4 / 10 | |
| 1.1.18 | 4 / 10 | |
| 1.1.17 | 4 / 10 | |
| 1.1.16 | 4 / 10 | |
| 1.1.14 | 4 / 10 | |
| 1.1.13 | 4 / 10 | |
| 1.1.12 | 4 / 10 | |
| 1.1.9 | 4 / 10 | |
| 1.1.8 | 4 / 10 | |
| 1.1.7 | 4 / 10 | |
| 1.1.6 | 4 / 10 | |
| 1.1.4 | 4 / 10 | |
| 1.1.2 | 4 / 10 | |
| 1.1.1 | 4 / 10 | |
| 1.0.79 | 4 / 10 | |
| 1.0.78 | 4 / 10 | |
| 1.0.77 | 4 / 10 | |
| 1.0.76 | 4 / 10 | |
| 1.0.75 | 4 / 10 | |
| 1.0.74 | 4 / 10 | |
| 1.0.73 | 4 / 10 | |
| 1.0.72 | 4 / 10 | |
| 1.0.71 | 4 / 10 | |
| 1.0.70 | 4 / 10 | |
| 1.0.69 | 4 / 10 | |
| 1.0.68 | 4 / 10 | |
| 1.0.67 | 4 / 10 | |
| 1.0.65 | 4 / 10 | |
| 1.0.64 | 4 / 10 | |
| 1.0.63 | 4 / 10 | |
| 1.0.62 | 4 / 10 | |
| 1.0.61 | 4 / 10 | |
| 1.0.60 | 4 / 10 | |
| 1.0.59 | 4 / 10 | |
| 1.0.58 | 4 / 10 | |
| 1.0.57 | 4 / 10 | |
| 1.0.56 | 4 / 10 | |
| 1.0.55 | 4 / 10 | |
| 1.0.54 | 4 / 10 | |
| 1.0.53 | 4 / 10 | |
| 1.0.52 | 4 / 10 | |
| 1.0.51 | 4 / 10 | |
| 1.0.50 | 4 / 10 | |
| 1.0.49 | 4 / 10 | |
| 1.0.48 | 4 / 10 | |
| 1.0.47 | 4 / 10 | |
| 1.0.46 | 4 / 10 | |
| 1.0.45 | 4 / 10 | |
| 1.0.44 | 4 / 10 | |
| 1.0.43 | 4 / 10 | |
| 1.0.42 | 4 / 10 | |
| 1.0.41 | 4 / 10 | |
| 1.0.40 | 4 / 10 | |
| 1.0.39 | 4 / 10 | |
| 1.0.38 | 4 / 10 | |
| 1.0.37 | 4 / 10 | |
| 1.0.36 | 4 / 10 | |
| 1.0.35 | 4 / 10 | |
| 1.0.34 | 4 / 10 | |
| 1.0.33 | 4 / 10 | |
| 1.0.32 | 4 / 10 | |
| 1.0.31 | 4 / 10 | |
| 1.0.30 | 4 / 10 | |
| 1.0.29 | 4 / 10 | |
| 1.0.28 | 4 / 10 | |
| 1.0.27 | 4 / 10 | |
| 1.0.26 | 4 / 10 | |
| 1.0.25 | 4 / 10 | |
| 1.0.24 | 4 / 10 | |
| 1.0.23 | 4 / 10 | |
| 1.0.22 | 4 / 10 | |
| 1.0.21 | 4 / 10 |
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.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.