@kb-labs/rest-api-app
REST API application for KB Labs, providing HTTP endpoints for plugin functionality
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): env-spread is in a subprocess spawn for DevKit CLI; passing process.env to child processes is standard and expected here. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs are localhost/127.0.0.1 in a plugin network permissions manifest for internal IPC — not exfiltration. | ai | |
| provenance | missing-githead | AI (provenance): Likely CI/CD environment change; publisher has strong track record and no other risk signals present. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Same monorepo/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fastify-plugin | AI (phantom-deps): Same monorepo/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger | AI (phantom-deps): Same monorepo/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/websocket | AI (phantom-deps): Same monorepo/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fastify/swagger-ui | AI (phantom-deps): Same monorepo/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Declared in deps, referenced via config; monorepo pattern makes direct import unnecessary. | ai | |
| phantom-deps | phantom-dep:@kb-labs/plugin-runtime | AI (phantom-deps): Same org scope; monorepo indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:@kb-labs/workflow-engine | AI (phantom-deps): Same org scope; monorepo indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:@kb-labs/workflow-contracts | AI (phantom-deps): Same org scope; monorepo indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:@kb-labs/plugin-execution-factory | AI (phantom-deps): Same org scope; monorepo indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:@kb-labs/core-tenant | AI (phantom-deps): Same org scope; monorepo indirect usage pattern. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Same monorepo/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Same monorepo/config-reference pattern; stable false positive for this package. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 2.94.0 | 34 / 8 | |
| 2.93.0 | 34 / 8 | |
| 2.89.0 | 34 / 8 | |
| 2.88.0 | 34 / 8 | |
| 2.87.0 | 34 / 8 | |
| 2.82.0 | 34 / 8 | |
| 2.81.0 | 34 / 8 | |
| 2.80.0 | 34 / 8 | |
| 2.79.0 | 34 / 8 | |
| 2.77.0 | 34 / 8 | |
| 2.75.0 | 34 / 8 | |
| 2.74.0 | 34 / 8 | |
| 2.73.0 | 34 / 8 | |
| 2.68.0 | 34 / 8 | |
| 2.67.0 | 34 / 8 | |
| 2.66.0 | 34 / 8 | |
| 2.65.0 | 34 / 8 | |
| 2.64.0 | 34 / 8 | |
| 2.62.0 | 34 / 8 | |
| 2.61.0 | 34 / 8 | |
| 2.60.0 | 34 / 8 | |
| 2.59.0 | 34 / 8 | |
| 2.58.0 | 34 / 8 | |
| 2.57.0 | 34 / 8 | |
| 2.56.0 | 34 / 8 | |
| 2.55.0 | 34 / 8 | |
| 2.54.0 | 34 / 8 | |
| 2.53.0 | 34 / 8 | |
| 2.47.0 | 34 / 8 | |
| 2.46.0 | 34 / 8 | |
| 2.45.0 | 34 / 8 | |
| 2.44.0 | 34 / 8 | |
| 2.43.0 | 34 / 8 | |
| 2.42.0 | 34 / 8 | |
| 2.41.0 | 34 / 8 | |
| 2.40.0 | 34 / 8 | |
| 2.39.0 | 34 / 8 | |
| 2.38.0 | 34 / 8 | |
| 2.37.0 | 34 / 8 | |
| 2.36.0 | 34 / 8 | |
| 2.35.0 | 34 / 8 | |
| 2.34.0 | 34 / 8 | |
| 2.33.0 | 34 / 8 | |
| 2.32.0 | 34 / 8 | |
| 2.31.0 | 34 / 8 | |
| 2.30.0 | 34 / 8 | |
| 2.29.0 | 34 / 8 | |
| 2.28.0 | 34 / 8 | |
| 2.25.0 | 34 / 8 | |
| 2.23.0 | 34 / 8 | |
| 2.22.0 | 34 / 8 |
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
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.88.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.87.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.82.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.80.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.75.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.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.67.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.65.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.64.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.62.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.61.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.59.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.58.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.57.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.56.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.55.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.54.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.47.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.46.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.44.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.43.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.42.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.40.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.39.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.37.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.36.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.35.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.34.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.32.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.30.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.29.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.25.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.22.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.