← Home

@e9n/pi-cron

npm Repository Homepage

Cron scheduler extension for pi — schedule recurring prompts as isolated subprocesses

2
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

e9n

Keywords

pi-package

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Passing process.env to child_process.spawn is standard for subprocess scheduling; not a secret-leak risk in this context. ai

Versions (showing 2 of 2)

Version Deps Published
0.2.1 0 / 2
0.2.0 0 / 2

v0.2.1

2 findings
HIGH env-spread: src/scheduler.ts:99 semgrep

Spreading entire process.env into an object — may capture all secrets 97 | cwd, 98 | stdio: ["ignore", "pipe", "pipe"], > 99 | env: { ...process.env }, 100 | timeout: timeoutMs, 101 | });

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