@keymanapp/kmc-generate
Keyman Developer generate module
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@keymanapp/common-types | AI (dependencies): Sibling monorepo package pinned to same version; expected pattern for @keymanapp releases. | ai | |
| dependencies | unvetted-dep:@keymanapp/developer-utils | AI (dependencies): Sibling monorepo package pinned to same version; expected pattern for @keymanapp releases. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 18.0.249 | 4 / 9 | |
| 18.0.248 | 4 / 9 | |
| 18.0.247 | 4 / 9 | |
| 18.0.246 | 4 / 9 | |
| 18.0.245 | 4 / 9 | |
| 18.0.243 | 4 / 9 | |
| 18.0.242 | 4 / 9 | |
| 18.0.241 | 4 / 9 | |
| 18.0.240 | 4 / 9 | |
| 18.0.239 | 4 / 9 | |
| 18.0.238 | 4 / 9 | |
| 18.0.237 | 4 / 9 | |
| 18.0.236 | 4 / 9 |
v18.0.249
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.248
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.247
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.246
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.245
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v18.0.243
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.