@kb-labs/workflow-runtime
Runtime adapters and step executors for the KB Labs workflow engine.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@kb-labs/workflow-steps | AI (phantom-deps): Same-org internal package, likely re-exported rather than directly imported. | ai | |
| provenance | missing-githead | AI (provenance): Consistent with normal monorepo publish variance from trusted high-volume publisher. | ai | |
| phantom-deps | phantom-dep:@kb-labs/workflow-builtins | AI (phantom-deps): Workspace dependency; same-org scope; phantom-dep heuristic inapplicable to monorepo patterns. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): Config-file reference; pino is a logging library commonly used indirectly via transitive deps. | ai | |
| bogus-package | bogus-package | AI (bogus-package): New scoped monorepo package; missing repo/keywords/inflated semver are typical for internal KB Labs packages. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 2.107.0 | 13 / 9 | |
| 2.106.0 | 13 / 9 | |
| 2.105.0 | 13 / 9 | |
| 2.104.0 | 13 / 9 | |
| 2.103.0 | 13 / 9 | |
| 2.102.0 | 13 / 9 | |
| 2.101.0 | 13 / 9 | |
| 2.100.0 | 13 / 9 | |
| 2.98.0 | 13 / 9 | |
| 2.96.0 | 13 / 9 | |
| 2.94.0 | 13 / 9 | |
| 2.93.0 | 13 / 9 | |
| 2.89.0 | 13 / 9 | |
| 2.88.0 | 13 / 9 | |
| 2.87.0 | 13 / 9 | |
| 2.82.0 | 13 / 9 | |
| 2.81.0 | 13 / 9 | |
| 2.80.0 | 13 / 9 | |
| 2.79.0 | 13 / 9 | |
| 2.77.0 | 13 / 9 | |
| 2.75.0 | 13 / 9 | |
| 2.74.0 | 13 / 9 | |
| 2.73.0 | 13 / 9 | |
| 2.68.0 | 13 / 9 | |
| 2.67.0 | 13 / 9 | |
| 2.66.0 | 13 / 9 | |
| 2.65.0 | 13 / 9 | |
| 2.64.0 | 13 / 9 | |
| 2.62.0 | 13 / 9 | |
| 2.61.0 | 13 / 9 | |
| 2.60.0 | 13 / 9 | |
| 2.59.0 | 13 / 9 | |
| 2.58.0 | 13 / 9 | |
| 2.57.0 | 13 / 9 | |
| 2.56.0 | 13 / 9 | |
| 2.55.0 | 13 / 9 | |
| 2.54.0 | 13 / 9 | |
| 2.53.0 | 13 / 9 | |
| 2.47.0 | 13 / 9 | |
| 2.46.0 | 13 / 9 | |
| 2.45.0 | 13 / 9 | |
| 2.44.0 | 13 / 9 | |
| 2.43.0 | 13 / 9 | |
| 2.42.0 | 13 / 9 | |
| 2.41.0 | 13 / 9 | |
| 2.40.0 | 13 / 9 | |
| 2.39.0 | 13 / 9 | |
| 2.38.0 | 13 / 9 | |
| 2.37.0 | 13 / 9 | |
| 2.36.0 | 13 / 9 | |
| 2.35.0 | 13 / 9 |
v2.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.98.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.96.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.43.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.