@ooneex/cli
Interactive CLI toolkit for scaffolding Ooneex projects, modules, controllers, services, repositories, and more with customizable code generation templates
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@ooneex/validation | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:@ooneex/linear | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:@ooneex/logger | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:@ooneex/app-env | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:@ooneex/command | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:@ooneex/migrations | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:@ooneex/role | AI (phantom-deps): Same-org dep; phantom-dep heuristic fires on CLI packages that load modules indirectly. | ai | |
| phantom-deps | phantom-dep:@ooneex/seeds | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:@ooneex/utils | AI (phantom-deps): Same-org dep; stable false positive for this package's indirect loading pattern. | ai | |
| phantom-deps | phantom-dep:autocannon | AI (phantom-deps): autocannon is likely bundled into dist/index.js rather than directly imported; phantom-dep is a false positive here. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Base64 WASM binary from bundled hdr-histogram-js; stable across versions of this package. | ai | |
| phantom-deps | phantom-dep:@logtail/node | AI (phantom-deps): Logging dep likely referenced in config/template files rather than direct imports; stable false positive for this CLI scaffolding package. | ai | |
| phantom-deps | phantom-dep:@ooneex/http-status | AI (phantom-deps): Same-org dep used in generated templates/config; not a direct import but legitimately declared. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped org package @ooneex/cli; Levenshtein match to 'joi' is coincidental, no impersonation intent. | ai |
Versions (showing 94 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.40.1 | 9 / 1 | |
| 1.40.0 | 9 / 1 | |
| 1.38.2 | 9 / 1 | |
| 1.38.1 | 9 / 1 | |
| 1.38.0 | 9 / 1 | |
| 1.37.0 | 9 / 1 | |
| 1.36.5 | 9 / 1 | |
| 1.36.4 | 9 / 1 | |
| 1.36.3 | 9 / 1 | |
| 1.36.2 | 9 / 1 | |
| 1.36.1 | 9 / 1 | |
| 1.36.0 | 9 / 1 | |
| 1.35.3 | 9 / 1 | |
| 1.35.2 | 9 / 1 | |
| 1.35.1 | 9 / 1 | |
| 1.35.0 | 9 / 1 | |
| 1.34.1 | 9 / 1 | |
| 1.34.0 | 9 / 1 | |
| 1.33.3 | 8 / 1 | |
| 1.33.2 | 8 / 1 | |
| 1.33.1 | 8 / 1 | |
| 1.33.0 | 8 / 1 | |
| 1.32.0 | 8 / 1 | |
| 1.31.1 | 6 / 1 | |
| 1.31.0 | 6 / 1 | |
| 1.30.0 | 6 / 1 | |
| 1.29.1 | 6 / 1 | |
| 1.29.0 | 6 / 1 | |
| 1.28.4 | 6 / 1 | |
| 1.28.3 | 6 / 1 | |
| 1.28.2 | 6 / 1 | |
| 1.28.1 | 6 / 1 | |
| 1.28.0 | 7 / 1 | |
| 1.27.0 | 7 / 1 | |
| 1.26.3 | 7 / 1 | |
| 1.26.2 | 7 / 1 | |
| 1.26.1 | 7 / 1 | |
| 1.26.0 | 7 / 1 | |
| 1.25.0 | 7 / 1 | |
| 1.24.0 | 7 / 1 | |
| 1.23.1 | 6 / 1 | |
| 1.23.0 | 6 / 1 | |
| 1.22.0 | 6 / 1 | |
| 1.21.0 | 6 / 1 | |
| 1.20.3 | 6 / 1 | |
| 1.20.2 | 6 / 1 | |
| 1.20.1 | 6 / 1 | |
| 1.20.0 | 6 / 1 | |
| 1.19.0 | 6 / 1 | |
| 1.18.0 | 6 / 1 | |
| 1.17.10 | 6 / 1 | |
| 1.17.9 | 6 / 1 | |
| 1.17.8 | 6 / 1 | |
| 1.17.7 | 6 / 1 | |
| 1.17.6 | 6 / 1 | |
| 1.17.5 | 6 / 1 | |
| 1.17.4 | 6 / 1 | |
| 1.17.2 | 6 / 1 | |
| 1.17.1 | 6 / 1 | |
| 1.17.0 | 6 / 1 | |
| 1.16.0 | 6 / 1 | |
| 1.7.0 | 11 / 1 | |
| 1.6.1 | 11 / 1 | |
| 1.6.0 | 11 / 1 | |
| 1.4.0 | 11 / 1 | |
| 1.3.1 | 11 / 1 | |
| 1.3.0 | 11 / 1 | |
| 1.2.17 | 11 / 1 | |
| 1.2.16 | 11 / 1 | |
| 1.2.15 | 11 / 1 | |
| 1.2.14 | 11 / 1 | |
| 1.2.13 | 11 / 1 | |
| 1.2.12 | 11 / 1 | |
| 1.2.11 | 11 / 1 | |
| 1.2.10 | 11 / 1 | |
| 1.2.9 | 11 / 1 | |
| 1.2.8 | 11 / 1 | |
| 1.2.7 | 11 / 1 | |
| 1.2.6 | 11 / 1 | |
| 1.2.5 | 11 / 1 | |
| 1.2.3 | 11 / 1 | |
| 1.2.2 | 11 / 1 | |
| 1.2.1 | 11 / 1 | |
| 1.2.0 | 11 / 1 | |
| 1.1.11 | 11 / 1 | |
| 1.1.10 | 11 / 1 | |
| 1.1.9 | 11 / 1 | |
| 1.1.8 | 11 / 1 | |
| 1.1.7 | 11 / 1 | |
| 1.1.6 | 11 / 1 | |
| 1.1.5 | 13 / 1 | |
| 1.1.4 | 12 / 1 | |
| 1.1.3 | 12 / 1 | |
| 1.1.2 | 10 / 1 |
v1.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.4
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.28.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
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.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
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.4.0
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.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.