@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 100 of 149)
| Version | Deps | Published |
|---|---|---|
| 3.4.10 | 19 / 6 | |
| 3.4.9 | 19 / 6 | |
| 3.4.8 | 19 / 6 | |
| 3.4.7 | 19 / 6 | |
| 3.4.6 | 19 / 6 | |
| 3.4.5 | 19 / 6 | |
| 3.4.4 | 19 / 6 | |
| 3.4.3 | 19 / 6 | |
| 3.4.2 | 19 / 6 | |
| 3.4.1 | 19 / 6 | |
| 3.4.0 | 19 / 6 | |
| 3.3.177 | 18 / 5 | |
| 3.3.176 | 17 / 5 | |
| 3.3.175 | 17 / 5 | |
| 3.3.174 | 17 / 5 | |
| 3.3.173 | 17 / 5 | |
| 3.3.172 | 17 / 5 | |
| 3.3.171 | 17 / 5 | |
| 3.3.169 | 17 / 5 | |
| 3.3.168 | 17 / 5 | |
| 3.3.167 | 17 / 5 | |
| 3.3.164 | 16 / 5 | |
| 3.3.161 | 16 / 5 | |
| 3.3.159 | 16 / 5 | |
| 3.3.153 | 16 / 5 | |
| 3.3.149 | 16 / 5 | |
| 3.3.148 | 16 / 5 | |
| 3.3.145 | 16 / 5 | |
| 3.3.142 | 15 / 5 | |
| 3.3.141 | 15 / 5 | |
| 3.3.140 | 15 / 5 | |
| 3.3.139 | 15 / 5 | |
| 3.3.138 | 15 / 5 | |
| 3.3.137 | 15 / 5 | |
| 3.3.136 | 15 / 5 | |
| 3.3.135 | 15 / 5 | |
| 3.3.134 | 15 / 5 | |
| 3.3.133 | 15 / 5 | |
| 3.3.132 | 15 / 5 | |
| 3.3.131 | 15 / 5 | |
| 3.3.130 | 15 / 5 | |
| 3.3.129 | 15 / 5 | |
| 3.3.128 | 15 / 5 | |
| 3.3.127 | 15 / 5 | |
| 3.3.126 | 15 / 5 | |
| 3.3.125 | 14 / 5 | |
| 3.3.124 | 14 / 5 | |
| 3.3.123 | 14 / 5 | |
| 3.3.122 | 14 / 5 | |
| 3.3.121 | 14 / 5 | |
| 3.3.119 | 14 / 5 | |
| 3.3.118 | 14 / 5 | |
| 3.3.117 | 14 / 5 | |
| 3.3.116 | 14 / 5 | |
| 3.3.115 | 14 / 5 | |
| 3.3.114 | 14 / 5 | |
| 3.3.113 | 14 / 5 | |
| 3.3.112 | 14 / 5 | |
| 3.3.111 | 14 / 5 | |
| 3.3.110 | 14 / 5 | |
| 3.3.109 | 14 / 5 | |
| 3.3.108 | 14 / 5 | |
| 3.3.107 | 14 / 5 | |
| 3.3.106 | 13 / 5 | |
| 3.3.105 | 13 / 5 | |
| 3.3.104 | 12 / 5 | |
| 3.3.103 | 12 / 5 | |
| 3.3.102 | 12 / 5 | |
| 3.3.101 | 12 / 5 | |
| 3.3.100 | 12 / 5 | |
| 3.3.99 | 12 / 5 | |
| 3.3.98 | 12 / 5 | |
| 3.3.97 | 12 / 5 | |
| 3.3.96 | 12 / 5 | |
| 3.3.95 | 12 / 5 | |
| 3.3.94 | 12 / 5 | |
| 3.3.93 | 12 / 5 | |
| 3.3.92 | 12 / 5 | |
| 3.3.91 | 12 / 5 | |
| 3.3.90 | 12 / 5 | |
| 3.3.89 | 12 / 5 | |
| 3.3.88 | 12 / 5 | |
| 3.3.87 | 12 / 5 | |
| 3.3.86 | 12 / 5 | |
| 3.3.85 | 12 / 5 | |
| 3.3.84 | 12 / 5 | |
| 3.3.83 | 12 / 5 | |
| 3.3.82 | 12 / 5 | |
| 3.3.81 | 12 / 5 | |
| 3.3.80 | 12 / 5 | |
| 3.3.79 | 12 / 5 | |
| 3.3.78 | 12 / 5 | |
| 3.3.77 | 12 / 5 | |
| 3.3.76 | 12 / 5 | |
| 3.3.75 | 12 / 5 | |
| 3.3.74 | 12 / 5 | |
| 3.3.73 | 12 / 5 | |
| 3.3.72 | 12 / 5 | |
| 3.3.71 | 12 / 5 | |
| 3.3.70 | 12 / 5 |
v3.4.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.