@computesdk/render
Render provider for ComputeSDK - managed cloud containers with automatic scaling
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:computesdk | AI (phantom-deps): Peer/config-level reference within the same SDK org; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@computesdk/provider | AI (phantom-deps): Same org scope dependency; phantom-dep heuristic fires on config references, not a real risk here. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.3.2 | 2 / 8 | |
| 1.3.1 | 2 / 8 | |
| 1.3.0 | 2 / 8 | |
| 1.2.22 | 2 / 8 | |
| 1.2.21 | 2 / 8 | |
| 1.2.20 | 2 / 8 | |
| 1.2.19 | 2 / 8 | |
| 1.2.18 | 2 / 8 | |
| 1.2.17 | 2 / 8 | |
| 1.2.16 | 2 / 8 | |
| 1.2.15 | 2 / 8 | |
| 1.2.14 | 2 / 8 | |
| 1.2.13 | 2 / 8 | |
| 1.2.12 | 2 / 8 | |
| 1.2.11 | 2 / 8 | |
| 1.2.9 | 2 / 8 | |
| 1.2.8 | 2 / 8 | |
| 1.2.6 | 2 / 8 | |
| 1.2.5 | 2 / 8 | |
| 1.2.4 | 2 / 8 | |
| 1.2.3 | 2 / 8 | |
| 1.2.2 | 2 / 8 | |
| 1.2.1 | 2 / 8 | |
| 1.2.0 | 2 / 8 | |
| 1.1.19 | 2 / 8 | |
| 1.1.18 | 2 / 8 | |
| 1.1.17 | 2 / 8 | |
| 1.1.15 | 2 / 8 | |
| 1.1.14 | 2 / 8 | |
| 1.1.13 | 2 / 8 | |
| 1.1.12 | 2 / 8 | |
| 1.1.11 | 2 / 8 | |
| 1.1.10 | 2 / 8 | |
| 1.1.9 | 2 / 8 | |
| 1.1.8 | 2 / 8 | |
| 1.1.7 | 2 / 8 | |
| 1.1.6 | 1 / 8 | |
| 1.1.5 | 1 / 8 | |
| 1.1.4 | 1 / 8 | |
| 1.1.3 | 1 / 8 | |
| 1.1.2 | 1 / 8 | |
| 1.1.1 | 1 / 8 | |
| 1.1.0 | 1 / 8 | |
| 1.0.1 | 1 / 8 | |
| 1.0.0 | 1 / 8 |
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
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. 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.