@oml/cli
The cli specific package
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used legitimately for AES-256-GCM IV/tag/ciphertext encoding in a crypto decryption helper; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:n3 | AI (phantom-deps): Config-referenced dependency, not a direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:langium-cli | AI (phantom-deps): Config-referenced build tool dependency; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @oml/cli is a scoped package in the @oml namespace; Levenshtein match to 'joi' is a false positive. | ai | |
| phantom-deps | phantom-dep:chevrotain | AI (phantom-deps): chevrotain is declared in dependencies and likely used transitively or via config; stable false positive for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.20.2 | 8 / 0 | |
| 0.20.1 | 8 / 0 | |
| 0.20.0 | 8 / 0 | |
| 0.19.3 | 8 / 0 | |
| 0.19.2 | 8 / 0 | |
| 0.19.1 | 8 / 0 | |
| 0.19.0 | 8 / 0 | |
| 0.18.1 | 8 / 0 | |
| 0.18.0 | 8 / 0 | |
| 0.17.0 | 8 / 0 | |
| 0.16.6 | 8 / 0 | |
| 0.16.5 | 8 / 0 | |
| 0.16.4 | 8 / 0 | |
| 0.16.3 | 8 / 0 | |
| 0.16.2 | 8 / 0 | |
| 0.16.1 | 8 / 0 | |
| 0.16.0 | 8 / 0 | |
| 0.15.0 | 8 / 0 | |
| 0.14.17 | 9 / 0 | |
| 0.14.16 | 9 / 0 | |
| 0.14.15 | 9 / 0 | |
| 0.14.14 | 9 / 0 | |
| 0.14.13 | 9 / 0 | |
| 0.14.12 | 8 / 0 | |
| 0.14.11 | 8 / 0 | |
| 0.14.10 | 8 / 0 | |
| 0.14.9 | 8 / 0 | |
| 0.14.8 | 8 / 0 | |
| 0.14.7 | 8 / 0 | |
| 0.14.6 | 8 / 0 | |
| 0.14.5 | 8 / 0 | |
| 0.14.4 | 8 / 0 | |
| 0.14.3 | 8 / 0 | |
| 0.14.2 | 7 / 0 | |
| 0.14.1 | 7 / 0 | |
| 0.14.0 | 7 / 0 | |
| 0.13.0 | 9 / 0 | |
| 0.12.0 | 9 / 0 | |
| 0.11.0 | 9 / 0 | |
| 0.10.0 | 9 / 0 | |
| 0.9.0 | 9 / 0 | |
| 0.8.0 | 8 / 0 | |
| 0.7.0 | 7 / 0 |
v0.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
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.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
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.14.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.