@glubean/sdk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established scoped SDK package with repo and exports; missing description is cosmetic, not a malware signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped private SDK with real usage; sparse metadata is a style choice, not a spam indicator. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.10.8 | 2 / 2 | |
| 0.10.7 | 2 / 2 | |
| 0.10.6 | 2 / 2 | |
| 0.10.5 | 2 / 2 | |
| 0.10.4 | 2 / 2 | |
| 0.10.3 | 2 / 2 | |
| 0.10.2 | 2 / 2 | |
| 0.10.1 | 2 / 2 | |
| 0.10.0 | 2 / 2 | |
| 0.9.5 | 2 / 2 | |
| 0.9.4 | 2 / 2 | |
| 0.9.3 | 2 / 2 | |
| 0.9.2 | 2 / 2 | |
| 0.9.1 | 2 / 2 | |
| 0.9.0 | 2 / 1 | |
| 0.8.4 | 2 / 1 | |
| 0.8.2 | 2 / 1 | |
| 0.8.1 | 2 / 1 | |
| 0.8.0 | 2 / 1 | |
| 0.7.0 | 2 / 1 | |
| 0.5.1 | 2 / 1 | |
| 0.5.0 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.2 | 2 / 1 | |
| 0.3.1 | 2 / 1 | |
| 0.3.0 | 1 / 1 | |
| 0.2.4 | 1 / 1 | |
| 0.2.3 | 1 / 1 | |
| 0.2.2 | 1 / 1 | |
| 0.2.1 | 1 / 1 | |
| 0.2.0 | 1 / 1 | |
| 0.1.39 | 1 / 1 | |
| 0.1.38 | 1 / 1 | |
| 0.1.37 | 1 / 1 | |
| 0.1.36 | 1 / 1 | |
| 0.1.35 | 1 / 1 | |
| 0.1.34 | 1 / 1 | |
| 0.1.33 | 1 / 1 | |
| 0.1.32 | 1 / 1 | |
| 0.1.31 | 1 / 1 | |
| 0.1.30 | 1 / 1 | |
| 0.1.29 | 1 / 1 | |
| 0.1.28 | 1 / 1 | |
| 0.1.27 | 1 / 1 | |
| 0.1.26 | 1 / 1 | |
| 0.1.25 | 1 / 1 | |
| 0.1.18 | 1 / 1 | |
| 0.1.15 | 1 / 1 | |
| 0.1.11 | 1 / 1 | |
| 0.1.10 | 1 / 1 | |
| 0.1.7 | 1 / 1 |
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
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.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.