← Home

@learncard/vc-api-plugin

npm Repository Homepage

[<img src="https://user-images.githubusercontent.com/2185016/190510561-294db809-09fd-4771-9749-6c0e0f4144fd.png" width="215"/>](https://learncard.com)

67
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

gerardoparcustard7smurflo2taylorbeestonjonny2lips

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation is a legitimate and verifiable supply chain improvement. ai
source-diff source-size-tripled AI (source-diff): Size increase aligns with CI/CD build artifact changes; no new deps or scripts added; SLSA attestation provides integrity guarantee. ai
bogus-package bogus-package AI (bogus-package): Scoped org package with legitimate repo and provenance; README/keyword signals are stable false positives for this package family. ai

Versions (showing 67 of 67)

Version Deps Published
1.1.27 2 / 9
1.1.26 2 / 9
1.1.25 2 / 9
1.1.24 2 / 9
1.1.23 2 / 9
1.1.22 2 / 9
1.1.21 2 / 9
1.1.20 2 / 9
1.1.19 2 / 9
1.1.18 2 / 9
1.1.17 2 / 9
1.1.16 2 / 9
1.1.14 2 / 9
1.1.13 2 / 9
1.1.12 2 / 9
1.1.9 2 / 9
1.1.8 2 / 9
1.1.7 2 / 9
1.1.6 2 / 9
1.1.4 2 / 9
1.1.2 2 / 9
1.1.1 2 / 9
1.0.55 2 / 9
1.0.54 2 / 9
1.0.53 2 / 9
1.0.52 2 / 9
1.0.51 2 / 9
1.0.50 2 / 9
1.0.49 2 / 9
1.0.48 2 / 9
1.0.47 2 / 9
1.0.46 2 / 9
1.0.44 2 / 9
1.0.43 2 / 9
1.0.42 2 / 9
1.0.41 2 / 9
1.0.40 2 / 9
1.0.39 2 / 9
1.0.38 2 / 9
1.0.37 2 / 9
1.0.36 2 / 9
1.0.35 2 / 9
1.0.34 2 / 9
1.0.33 2 / 9
1.0.32 2 / 9
1.0.31 2 / 9
1.0.30 2 / 9
1.0.29 2 / 9
1.0.28 2 / 9
1.0.27 2 / 9
1.0.26 2 / 9
1.0.25 2 / 9
1.0.24 2 / 9
1.0.23 2 / 9
1.0.22 2 / 9
1.0.21 2 / 9
1.0.20 2 / 9
1.0.19 2 / 9
1.0.18 2 / 9
1.0.17 2 / 9
1.0.16 2 / 9
1.0.15 2 / 9
1.0.14 2 / 9
1.0.13 2 / 9
1.0.12 2 / 9
1.0.11 2 / 9
1.0.10 2 / 9

v1.1.27

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.

v1.1.26

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.

v1.1.25

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.

v1.1.24

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.

v1.0.35

1 finding
LOW No provenance attestation provenance

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

v1.0.34

1 finding
LOW No provenance attestation provenance

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

v1.0.33

1 finding
LOW No provenance attestation provenance

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

v1.0.32

1 finding
LOW No provenance attestation provenance

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

v1.0.31

1 finding
LOW No provenance attestation provenance

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

v1.0.30

1 finding
LOW No provenance attestation provenance

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

v1.0.29

1 finding
LOW No provenance attestation provenance

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

v1.0.28

1 finding
LOW No provenance attestation provenance

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

v1.0.27

1 finding
LOW No provenance attestation provenance

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

v1.0.26

1 finding
LOW No provenance attestation provenance

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

v1.0.25

1 finding
LOW No provenance attestation provenance

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

v1.0.24

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.

v1.0.23

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.

v1.0.22

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.

v1.0.21

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.

v1.0.20

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.

v1.0.19

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.

v1.0.18

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.

v1.0.17

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.

v1.0.16

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.

v1.0.15

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.

v1.0.14

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.

v1.0.13

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.

v1.0.12

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.

v1.0.11

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.

v1.0.10

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.