@kb-labs/infra-worker-core
Infra worker plugin core for workspace/environment/snapshot lifecycle operations.
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:zod | AI (phantom-deps): Declared as runtime dep, likely used transitively or in config/type generation; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): React declared as dep for JSX/type support in infra plugin; not directly imported but expected for this package type. | ai | |
| phantom-deps | phantom-dep:@kb-labs/infra-worker-contracts | AI (phantom-deps): Same-org monorepo package; likely re-exported or used indirectly, stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 5 / 9 | |
| 2.93.0 | 5 / 9 | |
| 2.89.0 | 5 / 9 | |
| 2.7.0 | 5 / 9 | |
| 2.6.0 | 5 / 9 | |
| 0.5.0 | 5 / 9 |
v2.94.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: k.baranov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: k.baranov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: k.baranov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.