@cohostvip/cohost-node
Cohost API wrapper
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation provides stronger commit-level integrity than gitHead; missing gitHead is acceptable here. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.3.19 | 1 / 6 | |
| 0.3.3 | 0 / 6 | |
| 0.2.4 | 0 / 6 | |
| 0.2.0 | 0 / 6 | |
| 0.1.17 | 0 / 6 | |
| 0.1.16 | 0 / 6 | |
| 0.1.15 | 0 / 6 | |
| 0.1.14 | 0 / 6 | |
| 0.1.13 | 0 / 6 | |
| 0.1.12 | 0 / 6 | |
| 0.1.11 | 0 / 6 | |
| 0.1.10 | 0 / 6 | |
| 0.1.9 | 0 / 6 | |
| 0.1.8 | 0 / 6 | |
| 0.1.7 | 0 / 6 | |
| 0.1.6 | 0 / 6 | |
| 0.1.5 | 0 / 6 | |
| 0.1.4 | 0 / 6 | |
| 0.1.3 | 0 / 6 | |
| 0.1.2 | 0 / 6 | |
| 0.1.1 | 0 / 6 | |
| 0.1.0 | 0 / 6 | |
| 0.0.12 | 0 / 6 | |
| 0.0.11 | 0 / 6 | |
| 0.0.10 | 0 / 6 | |
| 0.0.9 | 0 / 6 | |
| 0.0.8 | 0 / 6 | |
| 0.0.7 | 0 / 6 | |
| 0.0.5 | 0 / 6 | |
| 0.0.4 | 0 / 6 | |
| 0.0.3 | 0 / 6 | |
| 0.0.2 | 0 / 6 | |
| 0.0.1 | 0 / 6 |
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.