@glubean/cli
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): @glubean/cli is a scoped org CLI tool, not a typosquat of joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a declared runtime dep used as a TypeScript runner, referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv referenced in config files; stable false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:archiver | AI (phantom-deps): archiver is a declared dep used for packaging; stable false positive for this CLI package. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 10 / 4 | |
| 0.4.0 | 10 / 4 | |
| 0.3.3 | 10 / 4 | |
| 0.3.2 | 10 / 4 | |
| 0.3.1 | 10 / 4 | |
| 0.3.0 | 10 / 4 | |
| 0.2.6 | 10 / 4 | |
| 0.2.5 | 10 / 3 | |
| 0.2.4 | 10 / 3 | |
| 0.2.3 | 10 / 3 | |
| 0.2.2 | 10 / 2 | |
| 0.2.1 | 10 / 2 | |
| 0.2.0 | 10 / 2 | |
| 0.1.82 | 10 / 2 | |
| 0.1.81 | 10 / 2 | |
| 0.1.80 | 10 / 2 | |
| 0.1.79 | 10 / 2 | |
| 0.1.78 | 10 / 2 | |
| 0.1.77 | 10 / 2 | |
| 0.1.76 | 10 / 2 | |
| 0.1.75 | 10 / 2 | |
| 0.1.74 | 10 / 2 | |
| 0.1.73 | 10 / 2 | |
| 0.1.71 | 10 / 2 | |
| 0.1.70 | 10 / 2 | |
| 0.1.69 | 10 / 2 | |
| 0.1.68 | 10 / 2 | |
| 0.1.67 | 10 / 2 | |
| 0.1.66 | 10 / 2 | |
| 0.1.65 | 10 / 2 | |
| 0.1.64 | 10 / 2 | |
| 0.1.63 | 10 / 2 | |
| 0.1.62 | 10 / 2 | |
| 0.1.61 | 10 / 2 | |
| 0.1.59 | 10 / 2 | |
| 0.1.58 | 10 / 2 | |
| 0.1.57 | 10 / 2 | |
| 0.1.56 | 10 / 2 | |
| 0.1.55 | 10 / 2 | |
| 0.1.54 | 10 / 2 | |
| 0.1.53 | 10 / 2 | |
| 0.1.52 | 10 / 2 | |
| 0.1.51 | 10 / 2 | |
| 0.1.50 | 10 / 2 | |
| 0.1.49 | 10 / 2 | |
| 0.1.48 | 10 / 2 | |
| 0.1.47 | 10 / 2 | |
| 0.1.34 | 10 / 2 | |
| 0.1.29 | 10 / 2 | |
| 0.1.28 | 10 / 2 | |
| 0.1.27 | 10 / 2 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.