← Home

@onmars/lunar-agent-claude

npm Repository Homepage

Claude CLI agent adapter for Lunar

34
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

marcelagotta

Keywords

lunaraiclaudeagentbun

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Fires in a test file saving/restoring process.env — standard test pattern, not a secret leak. ai
semgrep semgrep:env-bulk-read AI (semgrep): Agent adapter legitimately enumerates env to pass to subprocess; expected for this package's purpose. ai

Versions (showing 34 of 34)

Version Deps Published
0.15.1 1 / 0
0.15.0 1 / 0
0.14.0 1 / 0
0.13.0 1 / 0
0.12.2 1 / 0
0.12.1 1 / 0
0.12.0 1 / 0
0.11.4 1 / 0
0.11.3 1 / 0
0.11.2 1 / 0
0.11.1 1 / 0
0.11.0 1 / 0
0.10.3 1 / 0
0.10.2 1 / 0
0.10.1 1 / 0
0.10.0 1 / 0
0.9.1 1 / 0
0.9.0 1 / 0
0.8.0 1 / 0
0.7.0 1 / 0
0.6.2 1 / 0
0.6.1 1 / 0
0.6.0 1 / 0
0.5.0 1 / 0
0.4.7 1 / 0
0.4.5 1 / 0
0.4.4 1 / 0
0.4.3 1 / 0
0.4.2 1 / 0
0.4.1 1 / 0
0.4.0 1 / 0
0.3.0 1 / 0
0.2.0 1 / 0
0.1.0 1 / 0

v0.15.1

1 finding
LOW No provenance attestation provenance

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

v0.15.0

1 finding
LOW No provenance attestation provenance

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

v0.14.0

1 finding
LOW No provenance attestation provenance

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

v0.13.0

1 finding
LOW No provenance attestation provenance

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

v0.12.2

1 finding
LOW No provenance attestation provenance

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

v0.12.1

1 finding
LOW No provenance attestation provenance

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

v0.12.0

1 finding
LOW No provenance attestation provenance

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

v0.11.4

1 finding
LOW No provenance attestation provenance

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

v0.11.3

1 finding
LOW No provenance attestation provenance

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

v0.11.2

1 finding
LOW No provenance attestation provenance

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

v0.11.1

1 finding
LOW No provenance attestation provenance

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

v0.11.0

1 finding
LOW No provenance attestation provenance

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

v0.10.3

1 finding
LOW No provenance attestation provenance

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

v0.10.2

1 finding
LOW No provenance attestation provenance

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

v0.10.1

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.9.0

2 findings
HIGH env-spread: src/__tests__/adapter.test.ts:328 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/onmars-tech/lunar/blob/dfe9b83e22911dd262b113f9aabb2b636ac8cf1f/src/__tests__/adapter.test.ts#L328 326 | describe('buildEnv', () => { 327 | // Save original process.env > 328 | const originalEnv = { ...process.env } 329 | 330 | beforeEach(() => {

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.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.2

1 finding
LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

2 findings
HIGH env-spread: src/__tests__/adapter.test.ts:328 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/onmars-tech/lunar/blob/03605e375197f6c9c52f1bbf75a4830df9ee08ff/src/__tests__/adapter.test.ts#L328 326 | describe('buildEnv', () => { 327 | // Save original process.env > 328 | const originalEnv = { ...process.env } 329 | 330 | beforeEach(() => {

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.7

1 finding
LOW No provenance attestation provenance

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

v0.4.5

1 finding
LOW No provenance attestation provenance

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

v0.4.4

2 findings
HIGH env-spread: src/__tests__/adapter.test.ts:328 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/onmars-tech/lunar/blob/db55ec6836e512b8ad23057aa5077c92997a5b7b/src/__tests__/adapter.test.ts#L328 326 | describe('buildEnv', () => { 327 | // Save original process.env > 328 | const originalEnv = { ...process.env } 329 | 330 | beforeEach(() => {

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.3

1 finding
LOW No provenance attestation provenance

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

v0.4.2

1 finding
LOW No provenance attestation provenance

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

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

2 findings
HIGH env-spread: src/__tests__/adapter.test.ts:328 semgrep

Spreading entire process.env into an object — may capture all secrets 326 | describe('buildEnv', () => { 327 | // Save original process.env > 328 | const originalEnv = { ...process.env } 329 | 330 | beforeEach(() => {

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.1.0

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.