@openpolicy/cli
CLI to install OpenPolicy and print a setup prompt for coding agents
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/prompt-ceYDADjL.js | AI (source-diff): Bundled dist artifact from vite-plus build; long lines are minified npm deps (consola), not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/prompt-DUi4AHPD.js | AI (source-diff): Bundled minified output from consola dependency; standard CLI build artifact, not obfuscated malware. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @openpolicy/cli; Levenshtein match to 'joi' is coincidental, not a typosquat. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.0.34 | 0 / 5 | |
| 0.0.32 | 0 / 5 | |
| 0.0.31 | 0 / 5 | |
| 0.0.30 | 0 / 5 | |
| 0.0.29 | 0 / 4 | |
| 0.0.28 | 0 / 4 | |
| 0.0.27 | 0 / 4 | |
| 0.0.26 | 0 / 3 | |
| 0.0.25 | 0 / 3 | |
| 0.0.24 | 2 / 1 | |
| 0.0.23 | 2 / 3 | |
| 0.0.22 | 2 / 3 | |
| 0.0.21 | 2 / 3 | |
| 0.0.20 | 2 / 3 | |
| 0.0.19 | 2 / 3 | |
| 0.0.18 | 2 / 3 | |
| 0.0.17 | 2 / 3 | |
| 0.0.16 | 2 / 3 | |
| 0.0.15 | 2 / 3 | |
| 0.0.13 | 2 / 3 | |
| 0.0.3 | 2 / 2 | |
| 0.0.2 | 2 / 2 |
v0.0.34
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jamiedavenport.
Newly 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.
v0.0.32
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jamiedavenport.
Newly 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.
v0.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
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.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.