← Home

@kb-labs/devkit

Shared developer toolkit for KB Labs projects: TS/ESLint/Prettier/Vitest/Tsup presets and reusable GitHub Actions.

4
Versions
MIT
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

k.baranov

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Package is a config/tooling preset; no repo link and tiny main entry are expected for this package type. ai
install-scripts install-script:postinstall AI (install-scripts): Runs own bundled bin (kb-devkit-tsup-external --generate) for tsup config generation; stable dev-tooling pattern for this package. ai
phantom-deps phantom-dep:eslint-import-resolver-typescript AI (phantom-deps): Declared as runtime dep and used in ESLint config files; phantom-dep heuristic false positive for config-only usage. ai

Versions (showing 4 of 4)

Version Deps Published
2.94.0 7 / 15
2.89.0 7 / 15
2.68.0 7 / 15
1.1.0 7 / 14

v2.94.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.89.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: kb-devkit-tsup-external --generate || true

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.68.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.