@parall/agent-core
Shared agent runtime orchestration helpers for Parall
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/skills/parall-external-triggers.d.ts | AI (source-diff): Long line is a documentation string constant in a .d.ts file, not obfuscated code. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spread is followed by deletion of broker-owned secret keys; defensive pattern. | ai | |
| source-diff | obfuscated-file:dist/skills/parall-platform.d.ts | AI (source-diff): Long lines are human-readable markdown CLI docs embedded as a TypeScript string constant, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/skills/parall-schedules.d.ts | AI (source-diff): Long lines are human-readable markdown CLI docs embedded as a TypeScript string constant, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/skills/parall-wiki.d.ts | AI (source-diff): Long lines are human-readable markdown CLI docs embedded as a TypeScript string constant, not obfuscated code. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 1.50.0 | 11 / 2 | |
| 1.49.0 | 11 / 2 | |
| 1.48.0 | 11 / 2 | |
| 1.47.0 | 11 / 2 | |
| 1.46.0 | 11 / 2 | |
| 1.45.0 | 10 / 2 | |
| 1.44.0 | 10 / 2 | |
| 1.43.0 | 10 / 2 | |
| 1.42.1 | 10 / 2 | |
| 1.42.0 | 10 / 2 | |
| 1.41.0 | 10 / 2 | |
| 1.40.0 | 10 / 2 | |
| 1.39.0 | 10 / 2 | |
| 1.38.0 | 10 / 2 | |
| 1.37.0 | 10 / 2 | |
| 1.36.1 | 10 / 2 | |
| 1.36.0 | 10 / 2 | |
| 1.35.0 | 10 / 2 | |
| 1.34.0 | 10 / 2 | |
| 1.33.0 | 10 / 2 | |
| 1.32.1 | 10 / 2 | |
| 1.32.0 | 10 / 2 | |
| 1.31.0 | 1 / 2 | |
| 1.30.0 | 1 / 2 | |
| 1.29.3 | 1 / 2 | |
| 1.29.2 | 1 / 2 | |
| 1.29.1 | 1 / 2 | |
| 1.29.0 | 1 / 2 | |
| 1.28.1 | 1 / 2 | |
| 1.28.0 | 1 / 2 | |
| 1.27.0 | 1 / 2 | |
| 1.26.3 | 1 / 2 | |
| 1.26.2 | 1 / 2 | |
| 1.26.1 | 1 / 2 | |
| 1.26.0 | 1 / 2 | |
| 1.25.0 | 1 / 2 | |
| 1.24.0 | 1 / 2 | |
| 1.23.0 | 1 / 2 | |
| 1.22.0 | 1 / 2 | |
| 1.21.0 | 1 / 2 | |
| 1.20.2 | 1 / 2 | |
| 1.20.1 | 1 / 2 | |
| 1.20.0 | 1 / 2 | |
| 1.19.0 | 1 / 2 | |
| 1.18.1 | 1 / 2 | |
| 1.18.0 | 1 / 2 | |
| 1.17.0 | 1 / 2 | |
| 1.16.0 | 1 / 2 | |
| 1.15.1 | 1 / 2 | |
| 1.15.0 | 1 / 2 | |
| 1.14.5 | 1 / 2 | |
| 1.14.4 | 1 / 2 | |
| 1.14.3 | 1 / 2 | |
| 1.14.2 | 1 / 2 | |
| 1.14.1 | 1 / 2 | |
| 1.14.0 | 1 / 2 | |
| 1.13.1 | 1 / 2 |
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Spreading entire process.env into an object — may capture all secrets 144 | minted: { app_id: string; brand: string; token: string }, 145 | ): NodeJS.ProcessEnv { > 146 | const env: NodeJS.ProcessEnv = { ...process.env }; 147 | if (channel === 'feishu') { 148 | // Delete the broker-owned names case-insensitively: Windows env keys are
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Spreading entire process.env into an object — may capture all secrets 144 | minted: { app_id: string; brand: string; token: string }, 145 | ): NodeJS.ProcessEnv { > 146 | const env: NodeJS.ProcessEnv = { ...process.env }; 147 | if (channel === 'feishu') { 148 | // Delete the broker-owned names case-insensitively: Windows env keys are
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Spreading entire process.env into an object — may capture all secrets 144 | minted: { app_id: string; brand: string; token: string }, 145 | ): NodeJS.ProcessEnv { > 146 | const env: NodeJS.ProcessEnv = { ...process.env }; 147 | if (channel === 'feishu') { 148 | // Delete the broker-owned names case-insensitively: Windows env keys are
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Spreading entire process.env into an object — may capture all secrets 144 | minted: { app_id: string; brand: string; token: string }, 145 | ): NodeJS.ProcessEnv { > 146 | const env: NodeJS.ProcessEnv = { ...process.env }; 147 | if (channel === 'feishu') { 148 | // Delete the broker-owned names case-insensitively: Windows env keys are
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.