← Home

@wipcomputer/wip-ldm-os

npm Repository Homepage

LDM OS: identity, memory, and sovereignty infrastructure for AI agents

51
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

parkertoddbrooks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): Appears only in a test assertion validating that path-traversal names are rejected — not actual credential access. ai
semgrep semgrep:env-spread AI (semgrep): env-spread is in test scripts passing controlled env vars to child processes; not capturing secrets. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IP is 127.0.0.1 localhost health-check; not an external exfiltration endpoint. ai

Versions (showing 51 of 100)

View all versions
Version Deps Published
0.4.84 0 / 0
0.4.83 0 / 0
0.4.81 0 / 0
0.4.80 0 / 0
0.4.79 0 / 0
0.4.78 0 / 0
0.4.77 0 / 0
0.4.76 0 / 0
0.4.74 0 / 0
0.4.72 0 / 0
0.4.71 0 / 0
0.4.70 0 / 0
0.4.69 0 / 0
0.4.68 0 / 0
0.4.67 0 / 0
0.4.66 0 / 0
0.4.65 0 / 0
0.4.64 0 / 0
0.4.63 0 / 0
0.4.62 0 / 0
0.4.61 0 / 0
0.4.60 0 / 0
0.4.59 0 / 0
0.4.58 0 / 0
0.4.57 0 / 0
0.4.56 0 / 0
0.4.55 0 / 0
0.4.54 0 / 0
0.4.53 0 / 0
0.4.52 0 / 0
0.4.51 0 / 0
0.4.50 0 / 0
0.4.49 0 / 0
0.4.48 0 / 0
0.4.47 0 / 0
0.4.46 0 / 0
0.4.45 0 / 0
0.4.44 0 / 0
0.4.43 0 / 0
0.4.42 0 / 0
0.4.41 0 / 0
0.4.39 0 / 0
0.4.38 0 / 0
0.4.37 0 / 0
0.4.36 0 / 0
0.4.35 0 / 0
0.4.34 0 / 0
0.4.33 0 / 0
0.4.32 0 / 0
0.4.31 0 / 0
0.4.30 0 / 0

v0.4.84

7 findings
HIGH etc-passwd-access: scripts/test-bin-manifest.mjs:45 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/wipcomputer/wip-ldm-os-private/blob/da36cf9c45655ae08780365aae1d49d5d0260f71/scripts/test-bin-manifest.mjs#L45 43 | assert(validateDeclaration({ source: 'x' }).length > 0, 'missing name fails'); 44 | assert(validateDeclaration({ name: 'a.sh' }).length > 0, 'missing source fails'); > 45 | assert(validateDeclaration({ name: '../../etc/passwd', source: 'x' }).length > 0, 'name with .. fails'); 46 | assert(validateDeclaration({ name: 'sub/a.sh', source: 'x' }).length > 0, 'name with / fails'); 47 | assert(validateDeclaration({ name: 'a.sh', source: '../escape/a.sh' }).length > 0, 'source with .. fails');

HIGH env-spread: scripts/test-bin-manifest.mjs:229 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/wipcomputer/wip-ldm-os-private/blob/da36cf9c45655ae08780365aae1d49d5d0260f71/scripts/test-bin-manifest.mjs#L229 227 | try { 228 | return execFileSync('node', [cli, 'install'], { > 229 | env: { ...process.env, HOME: home, PATH: `${fakeBin}:${process.env.PATH}`, LDM_SELF_UPDATED: '1' }, 230 | encoding: 'utf-8', 231 | timeout: 30000,

HIGH env-spread: scripts/test-doctor-cron-target.mjs:89 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/wipcomputer/wip-ldm-os-private/blob/da36cf9c45655ae08780365aae1d49d5d0260f71/scripts/test-doctor-cron-target.mjs#L89 87 | try { 88 | return execFileSync('node', [cli, ...args], { > 89 | env: { ...process.env, HOME: home, PATH: `${fakeBin}:${process.env.PATH}`, LDM_SELF_UPDATED: '1' }, 90 | encoding: 'utf-8', 91 | timeout: 30000,

HIGH env-spread: scripts/test-ldm-install-preserves-foreign-bin.mjs:85 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/wipcomputer/wip-ldm-os-private/blob/da36cf9c45655ae08780365aae1d49d5d0260f71/scripts/test-ldm-install-preserves-foreign-bin.mjs#L85 83 | try { 84 | output = execFileSync('node', [cli, 'install'], { > 85 | env: { 86 | ...process.env, 87 | HOME: home,

HIGH env-spread: src/bridge/core.ts:156 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/wipcomputer/wip-ldm-os-private/blob/da36cf9c45655ae08780365aae1d49d5d0260f71/src/bridge/core.ts#L156 154 | `op read "op://Agent Secrets/OpenAI API/api key" 2>/dev/null`, 155 | { > 156 | env: { ...process.env, OP_SERVICE_ACCOUNT_TOKEN: saToken }, 157 | timeout: OP_CLI_TIMEOUT_MS, 158 | encoding: "utf-8",

HIGH env-spread: src/bridge/core.ts:1033 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/wipcomputer/wip-ldm-os-private/blob/da36cf9c45655ae08780365aae1d49d5d0260f71/src/bridge/core.ts#L1033 1031 | `${interpreter} "${scriptPath}" ${args}`, 1032 | { > 1033 | env: { ...process.env }, 1034 | timeout: SKILL_EXEC_TIMEOUT_MS, 1035 | maxBuffer: SKILL_EXEC_MAX_BUFFER,

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.

v0.4.83

1 finding
LOW No provenance attestation provenance

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

v0.4.81

1 finding
LOW No provenance attestation provenance

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

v0.4.80

1 finding
LOW No provenance attestation provenance

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

v0.4.79

1 finding
LOW No provenance attestation provenance

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

v0.4.78

1 finding
LOW No provenance attestation provenance

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

v0.4.77

1 finding
LOW No provenance attestation provenance

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

v0.4.76

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.

v0.4.74

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.

v0.4.72

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.

v0.4.71

1 finding
LOW No provenance attestation provenance

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

v0.4.70

1 finding
LOW No provenance attestation provenance

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

v0.4.69

1 finding
LOW No provenance attestation provenance

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

v0.4.68

1 finding
LOW No provenance attestation provenance

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

v0.4.67

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.

v0.4.66

1 finding
LOW No provenance attestation provenance

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

v0.4.65

1 finding
LOW No provenance attestation provenance

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

v0.4.64

1 finding
LOW No provenance attestation provenance

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

v0.4.63

1 finding
LOW No provenance attestation provenance

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

v0.4.62

1 finding
LOW No provenance attestation provenance

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

v0.4.61

1 finding
LOW No provenance attestation provenance

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

v0.4.60

1 finding
LOW No provenance attestation provenance

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

v0.4.59

1 finding
LOW No provenance attestation provenance

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

v0.4.58

1 finding
LOW No provenance attestation provenance

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

v0.4.57

1 finding
LOW No provenance attestation provenance

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

v0.4.56

1 finding
LOW No provenance attestation provenance

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

v0.4.55

1 finding
LOW No provenance attestation provenance

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

v0.4.54

1 finding
LOW No provenance attestation provenance

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

v0.4.53

1 finding
LOW No provenance attestation provenance

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

v0.4.52

1 finding
LOW No provenance attestation provenance

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

v0.4.51

1 finding
LOW No provenance attestation provenance

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

v0.4.50

1 finding
LOW No provenance attestation provenance

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

v0.4.49

1 finding
LOW No provenance attestation provenance

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

v0.4.48

1 finding
LOW No provenance attestation provenance

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

v0.4.47

1 finding
LOW No provenance attestation provenance

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

v0.4.46

1 finding
LOW No provenance attestation provenance

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

v0.4.45

1 finding
LOW No provenance attestation provenance

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

v0.4.44

1 finding
LOW No provenance attestation provenance

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

v0.4.43

1 finding
LOW No provenance attestation provenance

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

v0.4.42

1 finding
LOW No provenance attestation provenance

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

v0.4.41

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.

v0.4.39

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.

v0.4.38

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.

v0.4.37

1 finding
LOW No provenance attestation provenance

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

v0.4.36

1 finding
LOW No provenance attestation provenance

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

v0.4.35

1 finding
LOW No provenance attestation provenance

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

v0.4.34

1 finding
LOW No provenance attestation provenance

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

v0.4.33

1 finding
LOW No provenance attestation provenance

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

v0.4.32

1 finding
LOW No provenance attestation provenance

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

v0.4.31

1 finding
LOW No provenance attestation provenance

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

v0.4.30

1 finding
LOW No provenance attestation provenance

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