@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 — 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all 36 versions; org hasn't adopted Sigstore attestation, not a security signal. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 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.2.0 | 4 / 2 | |
| 1.0.1 | 4 / 2 | |
| 1.0.0 | 4 / 2 |
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.