← Home

@lobu/worker

npm Repository Homepage

Lobu worker runtime - run in your own Docker image or use our base image

49
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

buremba

Keywords

lobuworkeraiagent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:undici AI (phantom-deps): Known implicit runtime dependency, not a real concern. ai
dependencies unvetted-dep:@lobu/plugin-api AI (dependencies): First-party monorepo sibling package, version-pinned to same release. ai
dependencies unvetted-dep:@lobu/plugin-host AI (dependencies): First-party monorepo sibling package, version-pinned to same release. ai
dependencies unvetted-dep:@lobu/plugin-mcp AI (dependencies): First-party monorepo sibling package. ai
dependencies unvetted-dep:@lobu/plugin-media AI (dependencies): First-party monorepo sibling package. ai
dependencies unvetted-dep:@lobu/plugin-memory AI (dependencies): First-party monorepo sibling package. ai
dependencies unvetted-dep:@lobu/plugin-toolkit AI (dependencies): First-party monorepo sibling package. ai
dependencies unvetted-dep:@lobu/plugin-conversations AI (dependencies): First-party monorepo sibling package. ai
semgrep semgrep:env-bulk-read AI (semgrep): Same context: filtering process.env for child_process spawn is standard worker pattern. ai
semgrep semgrep:env-spread AI (semgrep): Worker runtime intentionally forwards full env to child processes; pattern is expected and documented. ai
phantom-deps phantom-dep:owletto AI (phantom-deps): owletto is a declared runtime dep; phantom-dep heuristic fires because it's used indirectly via config. ai
phantom-deps phantom-dep:@lobu/owletto-openclaw AI (phantom-deps): Same-org package used indirectly; phantom-dep false positive for this package. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IP (127.0.0.1) appears only in a JSDoc comment as a localhost example URL. ai
semgrep semgrep:etc-passwd-access AI (semgrep): Fires in test files exercising the just-bash hostcat feature; not production credential harvesting. ai
semgrep semgrep:base64-decode AI (semgrep): Fires in test assertions verifying base64 encoding behavior; no malicious payload. ai

Versions (showing 49 of 49)

Version Deps Published
14.3.0 18 / 2
14.0.0 11 / 2
13.4.0 11 / 2
13.3.0 11 / 2
13.2.0 11 / 2
13.1.0 11 / 2
13.0.0 11 / 2
12.1.0 11 / 2
12.0.0 11 / 2
11.3.0 11 / 2
11.2.0 11 / 2
11.1.0 11 / 2
11.0.0 11 / 2
10.2.0 11 / 2
10.1.0 11 / 2
10.0.0 11 / 2
9.4.1 11 / 2
9.4.0 11 / 2
9.3.0 11 / 2
9.1.1 11 / 2
9.1.0 11 / 2
9.0.0 11 / 2
8.0.0 11 / 2
7.2.0 11 / 2
7.1.0 11 / 2
7.0.0 11 / 2
6.1.1 11 / 2
6.0.0 11 / 2
5.0.0 11 / 2
4.3.0 11 / 2
4.2.0 13 / 2
3.5.0 13 / 2
3.4.3 13 / 2
3.4.2 13 / 2
3.4.1 13 / 2
3.4.0 13 / 2
3.3.0 13 / 2
3.2.0 13 / 2
3.1.1 13 / 2
3.1.0 13 / 2
3.0.19 13 / 2
3.0.16 13 / 2
3.0.13 13 / 2
3.0.12 13 / 2
3.0.8 13 / 2
3.0.7 13 / 2
3.0.6 13 / 2
3.0.5 13 / 2
2.8.0 13 / 2

v14.3.0

1 finding
LOW No provenance attestation provenance

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

v14.0.0

1 finding
LOW No provenance attestation provenance

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

v13.4.0

1 finding
LOW No provenance attestation provenance

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

v13.3.0

1 finding
LOW No provenance attestation provenance

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

v13.2.0

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.4.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.4.2

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.4.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.1.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.1.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: buremba → GitHub Actions (on 2026-04-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (buremba) on 2026-04-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v3.0.19

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: buremba → GitHub Actions (on 2026-04-10, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (buremba) on 2026-04-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v3.0.16

1 finding
LOW No provenance attestation provenance

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

v3.0.13

1 finding
LOW No provenance attestation provenance

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

v3.0.12

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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