@kb-labs/devlink-contracts
Contracts package for DevLink plugin — types, Zod schemas, flags.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Low-risk contracts/types package; no install scripts or suspicious code; provenance gap is a process concern, not a security threat. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 1 / 7 | |
| 2.93.0 | 1 / 7 | |
| 2.89.0 | 1 / 7 | |
| 2.86.0 | 1 / 7 | |
| 2.83.0 | 1 / 7 | |
| 2.81.0 | 1 / 7 | |
| 2.79.0 | 1 / 7 | |
| 2.77.0 | 1 / 7 | |
| 2.74.0 | 1 / 7 | |
| 2.73.0 | 1 / 7 | |
| 2.69.0 | 1 / 7 | |
| 2.68.0 | 1 / 7 | |
| 2.66.0 | 1 / 7 | |
| 2.60.0 | 1 / 7 | |
| 2.53.0 | 1 / 7 | |
| 2.45.0 | 1 / 7 | |
| 2.41.0 | 1 / 7 | |
| 2.38.0 | 1 / 7 | |
| 2.33.0 | 1 / 7 | |
| 2.31.0 | 1 / 7 | |
| 2.28.0 | 1 / 7 | |
| 2.23.0 | 1 / 7 | |
| 2.20.0 | 1 / 7 | |
| 2.18.0 | 1 / 7 | |
| 2.15.0 | 1 / 7 | |
| 2.12.0 | 1 / 7 | |
| 2.10.0 | 1 / 7 | |
| 2.9.0 | 1 / 7 | |
| 2.6.0 | 1 / 7 | |
| 1.5.0 | 1 / 7 |
v2.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.93.0
1 finding[Accepted risk] 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.86.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.83.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.81.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.79.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.77.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.74.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.73.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.69.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.68.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.66.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.60.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.53.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.45.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.41.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.38.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.33.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.31.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.28.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.23.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.20.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.18.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.15.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.12.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.10.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.9.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.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.