@learncard/cli
Test out learn card!
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 from custard7 to GitHub Actions CI/CD is backed by SLSA provenance attestation; consistent with org automation. | ai | |
| dependencies | unvetted-dep:pretty-repl | AI (dependencies): pretty-repl is a legitimate REPL utility; stable dependency across many versions of this CLI package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @learncard/cli from a known org; Levenshtein match to 'joi' is a false positive. | ai | |
| phantom-deps | phantom-dep:rollup | AI (phantom-deps): rollup is used as a build tool via config files, not directly imported in source — expected pattern for a CLI build tool. | ai | |
| phantom-deps | phantom-dep:@learncard/learn-cloud-plugin | AI (phantom-deps): Same-org plugin dependency; likely used indirectly via @learncard/init or similar aggregator. | ai |
Versions (showing 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 3.3.69 | 12 / 5 | |
| 3.3.68 | 12 / 5 | |
| 3.3.67 | 12 / 5 | |
| 3.3.66 | 12 / 5 | |
| 3.3.65 | 12 / 5 | |
| 3.3.64 | 12 / 5 | |
| 3.3.63 | 12 / 5 | |
| 3.3.62 | 12 / 5 | |
| 3.3.61 | 12 / 5 | |
| 3.3.60 | 12 / 5 | |
| 3.3.59 | 12 / 5 | |
| 3.3.58 | 12 / 5 | |
| 3.3.57 | 12 / 5 | |
| 3.3.56 | 12 / 5 | |
| 3.3.55 | 12 / 5 | |
| 3.3.54 | 12 / 5 | |
| 3.3.53 | 12 / 5 | |
| 3.3.52 | 12 / 5 | |
| 3.3.51 | 12 / 5 | |
| 3.3.50 | 12 / 5 | |
| 3.3.49 | 12 / 5 | |
| 3.3.48 | 12 / 5 | |
| 3.3.47 | 12 / 5 | |
| 3.3.46 | 12 / 5 | |
| 3.3.45 | 12 / 5 | |
| 3.3.44 | 12 / 5 | |
| 3.3.43 | 12 / 5 | |
| 3.3.42 | 12 / 5 | |
| 3.3.41 | 12 / 5 | |
| 3.3.40 | 12 / 5 | |
| 3.3.38 | 12 / 5 | |
| 3.3.37 | 12 / 5 | |
| 3.3.36 | 12 / 5 | |
| 3.3.35 | 12 / 5 | |
| 3.3.34 | 12 / 5 | |
| 3.3.33 | 12 / 5 | |
| 3.3.32 | 12 / 5 | |
| 3.3.31 | 12 / 5 | |
| 3.3.30 | 12 / 5 | |
| 3.3.29 | 12 / 5 | |
| 3.3.28 | 12 / 6 | |
| 3.3.27 | 12 / 6 | |
| 3.3.26 | 12 / 6 | |
| 3.3.25 | 12 / 6 | |
| 3.3.24 | 12 / 6 | |
| 3.3.23 | 12 / 6 | |
| 3.3.22 | 12 / 6 | |
| 3.3.21 | 12 / 6 | |
| 3.3.20 | 12 / 6 |
v3.3.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.