@parall/parall
OpenClaw channel plugin for Parall IM
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): env-spread is used to build a subprocess environment with specific overrides — a standard pattern for passing inherited env to child processes. No exfiltration path present. | ai | |
| typosquat | typosquat.levenshtein:parcel | AI (typosquat): '@parall/parall' is intentional branding for the Parall IM product under the parall-hq GitHub org; the similarity to 'parcel' is coincidental. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.32.0 | 2 / 3 | |
| 1.31.0 | 2 / 3 | |
| 1.30.0 | 2 / 3 | |
| 1.29.3 | 2 / 3 | |
| 1.29.2 | 2 / 3 | |
| 1.29.1 | 2 / 3 | |
| 1.29.0 | 2 / 3 | |
| 1.28.1 | 2 / 3 | |
| 1.28.0 | 2 / 3 | |
| 1.27.0 | 2 / 3 | |
| 1.26.3 | 2 / 3 | |
| 1.26.2 | 2 / 3 | |
| 1.26.1 | 2 / 3 | |
| 1.26.0 | 2 / 3 | |
| 1.25.0 | 2 / 3 | |
| 1.24.0 | 2 / 3 | |
| 1.23.0 | 2 / 3 | |
| 1.22.0 | 2 / 3 | |
| 1.21.0 | 2 / 3 | |
| 1.20.2 | 2 / 3 | |
| 1.20.1 | 2 / 3 | |
| 1.20.0 | 2 / 3 | |
| 1.19.0 | 2 / 3 | |
| 1.18.0 | 2 / 3 | |
| 1.17.0 | 2 / 3 | |
| 1.16.0 | 2 / 3 | |
| 1.15.1 | 2 / 3 | |
| 1.15.0 | 2 / 3 | |
| 1.14.5 | 2 / 3 | |
| 1.14.4 | 2 / 3 | |
| 1.14.3 | 2 / 3 | |
| 1.14.2 | 2 / 3 | |
| 1.14.1 | 2 / 3 | |
| 1.14.0 | 3 / 3 | |
| 1.13.1 | 3 / 3 | |
| 1.13.0 | 3 / 3 | |
| 1.12.0 | 2 / 3 |
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
2 findingsSpreading entire process.env into an object — may capture all secrets 44 | 45 | function buildWikiHelperEnv(params: StartWikiHelperParams, mountRoot: string): NodeJS.ProcessEnv { > 46 | return { 47 | ...process.env, 48 | PRLL_API_URL: params.parallUrl,
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.