@public-ui/kolibri-cli
CLI for executing some helpful commands for KoliBri projects.
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): m.oppitz is a known maintainer with 14 approved packages; manual publish alongside CI is plausible for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package maintains multiple major version branches (3.x and 4.x); dormancy on 3.x branch is expected. SLSA provenance attestation confirms legitimate CI/CD publishing. | ai | |
| license | copyleft-license:EUPL-1.2 | AI (license): EUPL-1.2 is the declared license for the entire KoliBri project by the German federal IT authority; this is a stable, intentional licensing choice, not a security risk. | ai | |
| phantom-deps | phantom-dep:loglevel | AI (phantom-deps): loglevel is declared as a runtime dependency and used via config/indirect imports in this CLI tool; not a phantom dep in practice. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): prettier is a declared runtime dependency used for formatting tasks in this CLI; referenced through config files as expected. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-organize-imports | AI (phantom-deps): prettier-plugin-organize-imports is a declared runtime dependency used as a prettier plugin; config-file-only reference is expected for plugins. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 10 / 15 | |
| 4.2.0 | 10 / 15 | |
| 4.1.4 | 10 / 17 | |
| 4.1.3 | 10 / 17 | |
| 4.1.2 | 10 / 17 | |
| 4.1.1 | 10 / 17 | |
| 4.1.0 | 10 / 17 | |
| 4.0.3 | 10 / 17 | |
| 4.0.2 | 10 / 15 | |
| 4.0.1 | 10 / 15 | |
| 4.0.0 | 10 / 15 | |
| 3.1.5 | 9 / 21 | |
| 3.1.4 | 9 / 21 | |
| 3.1.3 | 9 / 21 | |
| 3.1.2 | 9 / 21 | |
| 3.1.1 | 9 / 18 | |
| 3.1.0 | 9 / 18 | |
| 3.0.9 | 9 / 18 | |
| 3.0.8 | 9 / 19 | |
| 2.2.23 | 7 / 17 | |
| 2.2.22 | 7 / 17 | |
| 2.2.21 | 7 / 17 | |
| 2.2.20 | 7 / 17 | |
| 2.2.19 | 7 / 17 | |
| 2.2.18 | 7 / 17 |
v4.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.5
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.23
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.