@acorex/cli
CLI for Acorex projects
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 @acorex/cli is a legitimate CLI tool with 92 versions; edit-distance match to 'joi' is a false positive. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is explicitly listed in dependencies; phantom-dep heuristic misfired. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 21.1.7 | 3 / 3 | |
| 21.1.6 | 3 / 3 | |
| 21.1.5 | 3 / 3 | |
| 21.1.4 | 3 / 3 | |
| 21.1.3 | 3 / 3 | |
| 21.1.2 | 3 / 3 | |
| 21.1.1 | 3 / 3 | |
| 21.1.0 | 3 / 3 | |
| 21.0.25 | 3 / 3 | |
| 21.0.24 | 3 / 3 | |
| 21.0.23 | 3 / 3 | |
| 21.0.22 | 3 / 3 | |
| 21.0.21 | 3 / 3 | |
| 21.0.20 | 3 / 3 | |
| 21.0.19 | 3 / 3 | |
| 21.0.18 | 3 / 3 | |
| 21.0.17 | 3 / 3 | |
| 21.0.16 | 3 / 3 | |
| 21.0.15 | 3 / 3 | |
| 21.0.14 | 3 / 3 | |
| 21.0.13 | 3 / 3 | |
| 21.0.12 | 3 / 3 | |
| 21.0.11 | 3 / 3 | |
| 21.0.10 | 3 / 3 | |
| 21.0.9 | 3 / 3 | |
| 20.2.27 | 3 / 3 | |
| 20.2.26 | 3 / 3 | |
| 20.2.25 | 3 / 3 | |
| 20.2.24 | 3 / 3 | |
| 20.2.23 | 3 / 3 | |
| 20.2.22 | 3 / 3 | |
| 20.2.21 | 3 / 3 |
v21.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v20.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.