@polpo-ai/cli
Command-line client for Polpo — create/link/deploy cloud projects from your terminal.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @polpo-ai/cli; name similarity to joi is coincidental, not a typosquat attempt. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.7.18 | 5 / 2 | |
| 0.7.17 | 5 / 2 | |
| 0.7.16 | 5 / 2 | |
| 0.7.14 | 5 / 2 | |
| 0.7.13 | 5 / 2 | |
| 0.7.12 | 5 / 2 | |
| 0.7.11 | 5 / 2 | |
| 0.7.10 | 5 / 2 | |
| 0.7.9 | 5 / 2 | |
| 0.7.8 | 5 / 2 | |
| 0.7.7 | 5 / 2 | |
| 0.7.6 | 5 / 2 | |
| 0.7.5 | 5 / 2 | |
| 0.7.4 | 5 / 2 | |
| 0.7.3 | 5 / 2 | |
| 0.7.2 | 5 / 2 | |
| 0.7.1 | 5 / 2 | |
| 0.7.0 | 5 / 2 | |
| 0.6.32 | 5 / 2 | |
| 0.6.31 | 5 / 2 | |
| 0.6.30 | 5 / 2 | |
| 0.6.29 | 5 / 2 | |
| 0.6.28 | 5 / 2 | |
| 0.6.27 | 5 / 2 | |
| 0.6.26 | 5 / 2 | |
| 0.6.25 | 5 / 2 | |
| 0.6.24 | 5 / 2 | |
| 0.6.23 | 5 / 2 | |
| 0.6.22 | 5 / 2 | |
| 0.6.21 | 5 / 2 | |
| 0.6.20 | 5 / 2 | |
| 0.6.19 | 5 / 2 | |
| 0.6.18 | 5 / 2 | |
| 0.6.15 | 5 / 2 | |
| 0.6.14 | 5 / 2 | |
| 0.6.13 | 5 / 2 | |
| 0.6.12 | 5 / 2 | |
| 0.6.11 | 5 / 2 | |
| 0.6.10 | 5 / 2 | |
| 0.6.9 | 5 / 2 | |
| 0.6.7 | 5 / 2 | |
| 0.6.6 | 5 / 2 | |
| 0.6.5 | 5 / 2 | |
| 0.6.4 | 5 / 2 | |
| 0.6.3 | 5 / 2 | |
| 0.6.2 | 5 / 2 | |
| 0.6.1 | 5 / 2 | |
| 0.6.0 | 5 / 2 |
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.