open-plan-annotator
Fully local plugin for interactive plan annotation from your Agentic assistants
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): node install.cjs is a standard platform-binary setup script for this CLI tool; consistent across versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in CLI bin entry point — expected for a command-line tool. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type-only package; not imported at runtime by convention. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): CLI subprocess launcher pattern; spreading process.env to pass environment to child process is expected and benign for this tool. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.9.2 | 1 / 5 | |
| 1.9.1 | 1 / 5 | |
| 1.9.0 | 1 / 5 | |
| 1.8.7 | 1 / 5 | |
| 1.8.6 | 1 / 5 | |
| 1.8.5 | 1 / 5 | |
| 1.8.4 | 1 / 5 | |
| 1.8.3 | 1 / 5 | |
| 1.8.2 | 1 / 5 | |
| 1.8.1 | 1 / 5 | |
| 1.8.0 | 1 / 5 | |
| 1.6.3 | 1 / 5 | |
| 1.6.2 | 1 / 5 | |
| 1.6.1 | 1 / 5 | |
| 1.6.0 | 1 / 5 | |
| 1.5.5 | 1 / 5 | |
| 1.5.4 | 1 / 5 | |
| 1.5.3 | 1 / 5 | |
| 1.5.2 | 1 / 5 | |
| 1.5.1 | 1 / 5 | |
| 1.5.0 | 1 / 5 | |
| 1.4.2 | 1 / 4 | |
| 1.4.1 | 1 / 4 | |
| 1.4.0 | 1 / 4 | |
| 1.3.0 | 1 / 4 | |
| 1.2.1 | 1 / 4 | |
| 1.2.0 | 1 / 4 | |
| 1.1.0 | 1 / 4 | |
| 1.0.20 | 1 / 4 | |
| 1.0.6 | 2 / 3 | |
| 0.2.15 | 2 / 2 | |
| 0.2.9 | 2 / 2 |
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 134 | cwd, 135 | stdio: ["pipe", "pipe", "pipe"], > 136 | env: { 137 | ...process.env, 138 | ...options.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 134 | cwd, 135 | stdio: ["pipe", "pipe", "pipe"], > 136 | env: { 137 | ...process.env, 138 | ...options.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 134 | cwd, 135 | stdio: ["pipe", "pipe", "pipe"], > 136 | env: { 137 | ...process.env, 138 | ...options.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 134 | cwd, 135 | stdio: ["pipe", "pipe", "pipe"], > 136 | env: { 137 | ...process.env, 138 | ...options.env,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 125 | cwd, 126 | stdio: ["pipe", "pipe", "pipe"], > 127 | env: { 128 | ...process.env, 129 | OPEN_PLAN_HOST: "opencode",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 125 | cwd, 126 | stdio: ["pipe", "pipe", "pipe"], > 127 | env: { 128 | ...process.env, 129 | OPEN_PLAN_HOST: "opencode",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 125 | cwd, 126 | stdio: ["pipe", "pipe", "pipe"], > 127 | env: { 128 | ...process.env, 129 | OPEN_PLAN_HOST: "opencode",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 125 | cwd, 126 | stdio: ["pipe", "pipe", "pipe"], > 127 | env: { 128 | ...process.env, 129 | OPEN_PLAN_HOST: "opencode",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 125 | cwd, 126 | stdio: ["pipe", "pipe", "pipe"], > 127 | env: { 128 | ...process.env, 129 | OPEN_PLAN_HOST: "opencode",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
3 findingsSpreading entire process.env into an object — may capture all secrets 72 | stdio: ["pipe", "pipe", "inherit"], 73 | detached: true, > 74 | env: { 75 | ...process.env, 76 | OPEN_PLAN_HOST: process.env.OPEN_PLAN_HOST || "claude-code",
Spreading entire process.env into an object — may capture all secrets 125 | cwd, 126 | stdio: ["pipe", "pipe", "pipe"], > 127 | env: { 128 | ...process.env, 129 | OPEN_PLAN_HOST: "opencode",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
2 findingsScript: node install.cjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
2 findingsScript: node install.cjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
2 findingsScript: node install.cjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.