@kaizen-cib/plugin-kaizen-core-react
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Backstage plugins declare catalog dependencies in config, not imports. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-react | AI (phantom-deps): Backstage plugins declare catalog dependencies in config, not imports. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-scaffolder-react | AI (phantom-deps): Backstage plugins declare catalog dependencies in config, not imports. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo/internal package; minimal README and no external repo URL are normal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.2.11 | 8 / 5 | |
| 0.2.10 | 8 / 5 | |
| 0.2.9 | 8 / 5 | |
| 0.2.8 | 8 / 5 | |
| 0.2.7 | 8 / 5 | |
| 0.2.6 | 8 / 5 | |
| 0.2.5 | 8 / 5 | |
| 0.2.4 | 8 / 5 | |
| 0.2.3 | 8 / 5 | |
| 0.2.2 | 8 / 5 | |
| 0.2.1 | 8 / 5 | |
| 0.2.0 | 8 / 5 |
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.