@openape/apes
Unified CLI + MCP Server for OpenApe
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): node-pty permission fix is a standard postinstall pattern for this native binding; stable for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @openape/* scoped packages from the same monorepo; not third-party supply-chain risk. | ai | |
| dependencies | unvetted-dep:@lydell/node-pty | AI (dependencies): @lydell/node-pty is a well-known maintained fork of node-pty; appropriate for a CLI/shell tool like this. | ai | |
| phantom-deps | phantom-dep:@openape/proxy | AI (phantom-deps): Same-org scoped dep; likely used transitively or conditionally within the monorepo bundle. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.30.0 | 13 / 9 | |
| 1.28.12 | 11 / 9 | |
| 1.28.8 | 11 / 9 | |
| 1.28.7 | 11 / 9 | |
| 1.28.6 | 11 / 9 | |
| 1.28.3 | 11 / 9 | |
| 1.28.2 | 11 / 9 | |
| 1.27.0 | 11 / 9 | |
| 1.7.1 | 10 / 9 | |
| 1.3.1 | 10 / 9 | |
| 1.2.0 | 10 / 9 | |
| 1.1.1 | 10 / 9 | |
| 1.0.4 | 10 / 9 | |
| 1.0.2 | 10 / 9 | |
| 0.32.0 | 10 / 9 | |
| 0.31.1 | 10 / 9 | |
| 0.27.0 | 10 / 9 | |
| 0.18.0 | 10 / 9 | |
| 0.17.0 | 10 / 9 | |
| 0.15.1 | 10 / 9 | |
| 0.14.3 | 10 / 9 | |
| 0.14.1 | 10 / 9 | |
| 0.13.0 | 10 / 9 | |
| 0.12.2 | 9 / 9 | |
| 0.12.1 | 9 / 9 | |
| 0.12.0 | 9 / 9 | |
| 0.10.0 | 9 / 9 | |
| 0.9.0 | 9 / 9 | |
| 0.8.0 | 9 / 9 | |
| 0.6.1 | 8 / 9 | |
| 0.5.2 | 8 / 4 | |
| 0.5.1 | 8 / 4 | |
| 0.5.0 | 8 / 4 | |
| 0.4.0 | 7 / 4 | |
| 0.3.0 | 7 / 4 | |
| 0.2.1 | 7 / 4 | |
| 0.2.0 | 7 / 4 |
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
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.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
2 findingsScript: node scripts/fix-node-pty-perms.mjs
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
2 findingsScript: node scripts/fix-node-pty-perms.mjs
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsScript: node scripts/fix-node-pty-perms.mjs
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsScript: node scripts/fix-node-pty-perms.mjs
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsScript: node scripts/fix-node-pty-perms.mjs
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsScript: node scripts/fix-node-pty-perms.mjs
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.