@parall/claude-agent
Claude Code bridge runtime for self-hosted Parall agents
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Package is a Claude Code bridge runtime; spreading process.env to pass environment to a subprocess is expected and documented behavior, not exfiltration. | ai | |
| phantom-deps | phantom-dep:@parall/cli | AI (phantom-deps): @parall/cli is a same-org scoped dep in a monorepo release; not being directly imported in source is expected for a CLI bridge runtime package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.32.1 | 3 / 2 | |
| 1.32.0 | 3 / 2 | |
| 1.31.0 | 3 / 2 | |
| 1.30.0 | 3 / 2 | |
| 1.29.3 | 3 / 2 | |
| 1.29.2 | 3 / 2 | |
| 1.29.1 | 3 / 2 | |
| 1.29.0 | 3 / 2 | |
| 1.28.1 | 3 / 2 | |
| 1.28.0 | 3 / 2 | |
| 1.27.0 | 3 / 2 | |
| 1.26.3 | 3 / 2 | |
| 1.26.2 | 3 / 2 | |
| 1.26.1 | 3 / 2 | |
| 1.26.0 | 3 / 2 | |
| 1.25.0 | 3 / 2 | |
| 1.24.0 | 3 / 2 | |
| 1.23.0 | 3 / 2 | |
| 1.22.0 | 3 / 2 | |
| 1.21.0 | 3 / 2 | |
| 1.20.2 | 3 / 2 | |
| 1.20.1 | 3 / 2 | |
| 1.20.0 | 3 / 2 | |
| 1.19.0 | 3 / 2 | |
| 1.18.0 | 3 / 2 | |
| 1.17.0 | 3 / 2 | |
| 1.16.0 | 3 / 2 | |
| 1.15.1 | 3 / 2 |
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.2
2 findingsSpreading entire process.env into an object — may capture all secrets 32 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 33 | const args = this.buildArgs(sessionKey, bodyForAgent); > 34 | const env = { 35 | ...process.env, 36 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
2 findingsSpreading entire process.env into an object — may capture all secrets 32 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 33 | const args = this.buildArgs(sessionKey, bodyForAgent); > 34 | const env = { 35 | ...process.env, 36 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
2 findingsSpreading entire process.env into an object — may capture all secrets 32 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 33 | const args = this.buildArgs(sessionKey, bodyForAgent); > 34 | const env = { 35 | ...process.env, 36 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
2 findingsSpreading entire process.env into an object — may capture all secrets 32 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 33 | const args = this.buildArgs(sessionKey, bodyForAgent); > 34 | const env = { 35 | ...process.env, 36 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
2 findingsSpreading entire process.env into an object — may capture all secrets 32 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 33 | const args = this.buildArgs(sessionKey, bodyForAgent); > 34 | const env = { 35 | ...process.env, 36 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
2 findingsSpreading entire process.env into an object — may capture all secrets 32 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 33 | const args = this.buildArgs(sessionKey, bodyForAgent); > 34 | const env = { 35 | ...process.env, 36 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
2 findingsSpreading entire process.env into an object — may capture all secrets 79 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 80 | const args = this.buildArgs(sessionKey, bodyForAgent); > 81 | const env = { 82 | ...process.env, 83 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
2 findingsSpreading entire process.env into an object — may capture all secrets 46 | async *dispatch({ bodyForAgent, sessionKey, context }: DispatchOpts): AsyncIterable<RuntimeEvent> { 47 | const args = this.buildArgs(sessionKey, bodyForAgent); > 48 | const env = { 49 | ...process.env, 50 | HOME: this.opts.claudeHome,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.