← Home

@openclaw/lobster

npm Repository Homepage

Lobster workflow tool plugin (typed pipelines + resumable approvals)

22
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

steipetevincentkoc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Pattern is passing process.env to child process with an added key; not exfiltration. Stable for this package. ai

Versions (showing 22 of 22)

Version Deps Published
2026.3.13 1 / 0
2026.3.12 1 / 0
2026.3.11 1 / 0
2026.3.10 1 / 0
2026.3.7 1 / 0
2026.3.2 0 / 0
2026.3.1 0 / 0
2026.2.25 0 / 0
2026.2.24 0 / 0
2026.2.23 0 / 0
2026.2.22 0 / 0
2026.2.21 0 / 0
2026.2.19 0 / 1
2026.2.17 0 / 1
2026.2.15 0 / 1
2026.2.13 0 / 1
2026.2.12 0 / 1
2026.2.9 0 / 1
2026.2.6 0 / 1
2026.2.2 0 / 1
2026.2.1 0 / 1
2026.1.29 0 / 0

v2026.3.13

3 findings
HIGH env-spread: src/lobster-tool.ts:61 semgrep

Spreading entire process.env into an object — may capture all secrets 59 | const maxStdoutBytes = Math.max(1024, params.maxStdoutBytes); 60 | > 61 | const env = { ...process.env, LOBSTER_MODE: "tool" } as Record<string, string | undefined>; 62 | const nodeOptions = env.NODE_OPTIONS ?? ""; 63 | if (nodeOptions.includes("--inspect")) {

HIGH env-spread: src/windows-spawn.test.ts:98 semgrep

Spreading entire process.env into an object — may capture all secrets 96 | await fs.writeFile(scriptPath, "module.exports = {};\n", "utf8"); 97 | > 98 | const env = { 99 | ...process.env, 100 | PATH: `${binDir};${process.env.PATH ?? ""}`,

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.

v2026.3.12

1 finding
LOW No provenance attestation provenance

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

v2026.3.11

1 finding
LOW No provenance attestation provenance

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

v2026.3.10

1 finding
LOW No provenance attestation provenance

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

v2026.3.7

1 finding
LOW No provenance attestation provenance

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

v2026.3.2

1 finding
LOW No provenance attestation provenance

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

v2026.3.1

1 finding
LOW No provenance attestation provenance

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

v2026.2.25

1 finding
LOW No provenance attestation provenance

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

v2026.2.24

1 finding
LOW No provenance attestation provenance

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

v2026.2.23

1 finding
LOW No provenance attestation provenance

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

v2026.2.22

1 finding
LOW No provenance attestation provenance

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

v2026.2.21

1 finding
LOW No provenance attestation provenance

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

v2026.2.19

1 finding
LOW No provenance attestation provenance

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

v2026.2.17

1 finding
LOW No provenance attestation provenance

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

v2026.2.15

1 finding
LOW No provenance attestation provenance

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

v2026.2.13

1 finding
LOW No provenance attestation provenance

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

v2026.2.12

1 finding
LOW No provenance attestation provenance

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

v2026.2.9

1 finding
LOW No provenance attestation provenance

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

v2026.2.6

1 finding
LOW No provenance attestation provenance

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

v2026.2.2

1 finding
LOW No provenance attestation provenance

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

v2026.2.1

1 finding
LOW No provenance attestation provenance

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

v2026.1.29

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.