@tinycloud/sdk-core
Core TinyCloud SDK - shared interfaces and TinyCloud class
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tinycloud/bootstrap | AI (dependencies): First-party sibling package from same monorepo/publisher, version-locked. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an official same-org sibling, not a third-party addition. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Used indirectly via config files; heuristic false positive. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 36 versions; org hasn't adopted Sigstore attestation, not a security signal. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 2.9.0 | 13 / 4 | |
| 2.8.0 | 13 / 4 | |
| 2.7.0 | 13 / 4 | |
| 2.6.3 | 12 / 4 | |
| 2.6.2 | 12 / 4 | |
| 2.6.1 | 12 / 4 | |
| 2.6.0 | 12 / 4 | |
| 2.5.1 | 12 / 4 | |
| 2.5.0 | 12 / 4 | |
| 2.4.0 | 12 / 4 | |
| 2.3.0 | 11 / 4 | |
| 2.2.0 | 11 / 4 | |
| 2.1.0 | 5 / 4 | |
| 2.0.4 | 4 / 3 | |
| 2.0.3 | 4 / 3 | |
| 2.0.2 | 4 / 3 | |
| 2.0.1 | 4 / 2 | |
| 2.0.0 | 4 / 2 | |
| 1.7.0 | 4 / 2 | |
| 1.6.0 | 4 / 2 | |
| 1.5.0 | 4 / 2 | |
| 1.3.0 | 4 / 2 | |
| 1.2.0 | 4 / 2 | |
| 1.1.0 | 4 / 2 | |
| 1.0.1 | 4 / 2 | |
| 1.0.0 | 4 / 2 |
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.