@tinycloud/node-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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.cjs | AI (source-diff): Long base64 string is ENS normalization data from @ethersproject/hash; stable bundled dependency payload. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Same ENS normalization dataset in ESM build; not a malicious payload. | ai | |
| phantom-deps | phantom-dep:@tinycloud/web-core | AI (phantom-deps): Same-org scope dependency; likely used transitively or conditionally within the package. | ai | |
| phantom-deps | phantom-dep:siwe | AI (phantom-deps): siwe is a declared runtime dependency; phantom-dep heuristic misfires when imports are indirect or re-exported through bundled dist. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.9.0 | 4 / 3 | |
| 2.8.0 | 4 / 3 | |
| 2.7.0 | 4 / 3 | |
| 2.6.3 | 3 / 3 | |
| 2.6.2 | 3 / 3 | |
| 2.6.1 | 3 / 3 | |
| 2.6.0 | 3 / 3 | |
| 2.5.1 | 3 / 3 | |
| 2.5.0 | 3 / 3 | |
| 2.4.0 | 3 / 3 | |
| 2.3.0 | 3 / 3 | |
| 2.2.0 | 3 / 3 | |
| 2.1.0 | 3 / 3 | |
| 2.0.4 | 3 / 3 | |
| 2.0.3 | 3 / 3 | |
| 2.0.1 | 3 / 3 | |
| 2.0.0 | 3 / 3 | |
| 1.7.0 | 4 / 3 | |
| 1.6.0 | 4 / 3 | |
| 1.5.0 | 4 / 3 | |
| 1.4.1 | 4 / 3 | |
| 1.4.0 | 4 / 3 | |
| 1.3.0 | 4 / 3 | |
| 1.2.0 | 4 / 3 | |
| 1.1.0 | 4 / 2 | |
| 1.0.1 | 4 / 2 | |
| 1.0.0 | 4 / 2 |
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.