@checkstack/healthcheck-rcon-backend
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Private monorepo workspace package; missing metadata is expected, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal workspace package; no description is consistent across the @checkstack monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Internal plugin package; no provenance is consistent across all versions in this ecosystem. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.3.17 | 5 / 4 | |
| 0.3.16 | 5 / 4 | |
| 0.3.15 | 5 / 4 | |
| 0.3.14 | 5 / 4 | |
| 0.3.13 | 5 / 4 | |
| 0.3.12 | 5 / 4 | |
| 0.3.10 | 5 / 4 | |
| 0.3.9 | 5 / 4 | |
| 0.3.8 | 5 / 4 | |
| 0.3.4 | 5 / 4 | |
| 0.2.11 | 5 / 4 | |
| 0.2.10 | 5 / 4 | |
| 0.2.8 | 5 / 4 | |
| 0.2.4 | 5 / 4 | |
| 0.2.3 | 5 / 4 | |
| 0.2.1 | 5 / 4 | |
| 0.2.0 | 5 / 4 |
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.
v0.2.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.