@humanlayer/cli
HumanLayer CLI — daemon management and authentication
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 @humanlayer/cli has no relation to 'joi'; Levenshtein match is a false positive for this org-scoped CLI package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload and missing metadata are expected for a platform-binary-wrapper CLI package that delegates to optional platform-specific deps. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.24.1 | 0 / 1 | |
| 0.24.0 | 0 / 1 | |
| 0.23.0 | 0 / 1 | |
| 0.22.3 | 0 / 1 | |
| 0.22.2 | 0 / 1 | |
| 0.22.1 | 0 / 1 | |
| 0.22.0 | 0 / 1 | |
| 0.21.4 | 0 / 1 | |
| 0.21.3 | 0 / 1 | |
| 0.21.2 | 0 / 1 | |
| 0.21.1 | 0 / 1 | |
| 0.20.1 | 0 / 1 | |
| 0.19.1 | 0 / 1 | |
| 0.19.0 | 0 / 1 | |
| 0.18.6 | 0 / 1 | |
| 0.18.4 | 0 / 1 | |
| 0.18.3 | 0 / 1 | |
| 0.18.2 | 0 / 1 | |
| 0.18.1 | 0 / 1 | |
| 0.18.0 | 0 / 1 | |
| 0.17.2 | 0 / 1 | |
| 0.17.1 | 0 / 1 | |
| 0.17.0 | 0 / 1 | |
| 0.16.0 | 0 / 1 | |
| 0.15.5 | 0 / 1 | |
| 0.15.2 | 0 / 1 | |
| 0.15.1 | 0 / 1 | |
| 0.15.0 | 0 / 1 | |
| 0.14.3 | 0 / 1 | |
| 0.14.2 | 0 / 1 | |
| 0.14.1 | 0 / 1 | |
| 0.14.0 | 0 / 1 | |
| 0.13.4 | 0 / 1 | |
| 0.13.3 | 0 / 1 | |
| 0.13.2 | 0 / 1 | |
| 0.13.1 | 0 / 1 | |
| 0.13.0 | 0 / 1 | |
| 0.12.3 | 0 / 1 | |
| 0.12.2 | 0 / 1 | |
| 0.12.1 | 0 / 1 | |
| 0.11.5 | 0 / 1 | |
| 0.11.4 | 0 / 1 | |
| 0.11.3 | 0 / 1 | |
| 0.11.0 | 0 / 1 | |
| 0.10.5 | 0 / 1 | |
| 0.10.4 | 0 / 1 | |
| 0.10.3 | 0 / 1 | |
| 0.10.2 | 0 / 1 | |
| 0.10.1 | 0 / 1 | |
| 0.10.0 | 0 / 1 | |
| 0.9.1 | 0 / 1 |
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
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.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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
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.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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.