@commentray/code-commentray-static
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:sharp | AI (phantom-deps): sharp is a known native binding used implicitly via image processing pipeline; phantom-dep is expected. | ai | |
| phantom-deps | phantom-dep:png-to-ico | AI (phantom-deps): png-to-ico referenced in config/build pipeline; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): New package family; provenance absence is common and no other risk signals present. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.3.6 | 5 / 1 | |
| 0.3.5 | 5 / 1 | |
| 0.3.4 | 5 / 1 | |
| 0.3.3 | 5 / 1 | |
| 0.3.2 | 5 / 1 | |
| 0.3.1 | 5 / 1 | |
| 0.3.0 | 5 / 1 | |
| 0.2.0 | 5 / 1 | |
| 0.1.2 | 5 / 1 | |
| 0.1.1 | 5 / 1 | |
| 0.1.0 | 5 / 1 | |
| 0.0.9 | 5 / 1 | |
| 0.0.8 | 5 / 1 | |
| 0.0.6 | 3 / 1 | |
| 0.0.5 | 3 / 1 | |
| 0.0.4 | 3 / 1 |
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.