@soonspacejs/plugin-heat-cloud
Haet-cloud plugin for SoonSpace.js
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:UNLICENSED | AI (license): Proprietary commercial SDK plugin; UNLICENSED is intentional and consistent across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established plugin family; no provenance is consistent across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large closed-source commercial SDK family; sparse README and no public repo are expected for UNLICENSED plugins. | ai |
Versions (showing 100 of 178)
| Version | Deps | Published |
|---|---|---|
| 2.15.16 | 1 / 0 | |
| 2.15.15 | 1 / 0 | |
| 2.15.14 | 1 / 0 | |
| 2.15.13 | 1 / 0 | |
| 2.15.12 | 1 / 0 | |
| 2.15.11 | 1 / 0 | |
| 2.15.10 | 1 / 0 | |
| 2.15.9 | 1 / 0 | |
| 2.15.8 | 1 / 0 | |
| 2.15.7 | 1 / 0 | |
| 2.15.6 | 1 / 0 | |
| 2.15.5 | 1 / 0 | |
| 2.15.4 | 1 / 0 | |
| 2.15.2 | 1 / 0 | |
| 2.15.1 | 1 / 0 | |
| 2.15.0 | 1 / 0 | |
| 2.14.37 | 1 / 0 | |
| 2.14.35 | 1 / 0 | |
| 2.14.34 | 1 / 0 | |
| 2.14.33 | 1 / 0 | |
| 2.14.32 | 1 / 0 | |
| 2.14.31 | 1 / 0 | |
| 2.14.30 | 1 / 0 | |
| 2.14.29 | 1 / 0 | |
| 2.14.28 | 1 / 0 | |
| 2.14.27 | 1 / 0 | |
| 2.14.26 | 1 / 0 | |
| 2.14.24 | 1 / 0 | |
| 2.14.23 | 1 / 0 | |
| 2.14.21 | 1 / 0 | |
| 2.14.13 | 1 / 0 | |
| 2.14.12 | 1 / 0 | |
| 2.14.11 | 1 / 0 | |
| 2.14.10 | 1 / 0 | |
| 2.14.9 | 1 / 0 | |
| 2.14.8 | 1 / 0 | |
| 2.14.7 | 1 / 0 | |
| 2.14.6 | 1 / 0 | |
| 2.14.5 | 1 / 0 | |
| 2.14.4 | 1 / 0 | |
| 2.14.3 | 1 / 0 | |
| 2.14.2 | 1 / 0 | |
| 2.14.1 | 1 / 0 | |
| 2.14.0 | 1 / 0 | |
| 2.13.17 | 1 / 0 | |
| 2.13.16 | 1 / 0 | |
| 2.13.15 | 1 / 0 | |
| 2.13.14 | 1 / 0 | |
| 2.13.12 | 1 / 0 | |
| 2.13.11 | 1 / 0 | |
| 2.13.10 | 1 / 0 | |
| 2.13.9 | 1 / 0 | |
| 2.13.8 | 1 / 0 | |
| 2.13.7 | 1 / 0 | |
| 2.13.6 | 1 / 0 | |
| 2.13.5 | 1 / 0 | |
| 2.13.4 | 1 / 0 | |
| 2.13.2 | 1 / 0 | |
| 2.13.1 | 1 / 0 | |
| 2.13.0 | 1 / 0 | |
| 2.12.2 | 1 / 0 | |
| 2.12.1 | 1 / 0 | |
| 2.12.0 | 1 / 0 | |
| 2.11.71 | 1 / 0 | |
| 2.11.70 | 1 / 0 | |
| 2.11.69 | 1 / 0 | |
| 2.11.68 | 1 / 0 | |
| 2.11.67 | 1 / 0 | |
| 2.11.66 | 1 / 0 | |
| 2.11.65 | 1 / 0 | |
| 2.11.64 | 1 / 0 | |
| 2.11.63 | 1 / 0 | |
| 2.11.62 | 1 / 0 | |
| 2.11.61 | 1 / 0 | |
| 2.11.58 | 1 / 0 | |
| 2.11.57 | 1 / 0 | |
| 2.11.56 | 1 / 0 | |
| 2.11.55 | 1 / 0 | |
| 2.11.54 | 1 / 0 | |
| 2.11.53 | 1 / 0 | |
| 2.11.52 | 1 / 0 | |
| 2.11.51 | 1 / 0 | |
| 2.11.50 | 1 / 0 | |
| 2.11.49 | 1 / 0 | |
| 2.11.48 | 1 / 0 | |
| 2.11.47 | 1 / 0 | |
| 2.11.46 | 1 / 0 | |
| 2.11.45 | 1 / 0 | |
| 2.11.44 | 1 / 0 | |
| 2.11.43 | 1 / 0 | |
| 2.11.42 | 1 / 0 | |
| 2.11.41 | 1 / 0 | |
| 2.11.40 | 1 / 0 | |
| 2.11.39 | 1 / 0 | |
| 2.11.37 | 1 / 0 | |
| 2.11.36 | 1 / 0 | |
| 2.11.35 | 1 / 0 | |
| 2.11.34 | 1 / 0 | |
| 2.11.33 | 1 / 0 | |
| 2.11.32 | 1 / 0 |
v2.15.16
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chjxx) than the most recent previously approved version (jiangqi) on 2026-07-24, but chjxx is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.15.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chjxx) than the most recent previously approved version (jiangqi) on 2026-07-24, but chjxx is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.15.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jiangqi) than the most recent previously approved version (chjxx) on 2026-07-08, but jiangqi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.