@igniteui/cli-core
Base types and functionality for Ignite UI CLI
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI package manager legitimately uses child_process to invoke npm/yarn commands; stable pattern across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Template loader resolves paths from known basePath; standard plugin/template loading pattern for this CLI tool. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Infragistics maintains a large monorepo of related CLI packages; templated naming and sparse README are expected for this vendor. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 15.2.2 | 6 / 2 | |
| 15.2.1 | 6 / 2 | |
| 15.2.0 | 6 / 2 | |
| 15.1.0 | 6 / 2 | |
| 15.0.1 | 6 / 2 | |
| 15.0.0 | 6 / 2 | |
| 14.9.2 | 5 / 2 | |
| 14.9.1 | 5 / 2 | |
| 14.9.0 | 5 / 2 | |
| 14.8.5 | 5 / 2 | |
| 14.8.4 | 5 / 2 | |
| 14.8.3 | 5 / 2 | |
| 14.8.2 | 5 / 2 | |
| 14.8.1 | 5 / 2 | |
| 14.8.0 | 5 / 2 | |
| 14.7.1 | 5 / 2 | |
| 14.7.0 | 5 / 2 | |
| 14.6.6 | 5 / 2 | |
| 14.6.5 | 5 / 2 |
v15.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.