@combos-fun/plugin-renderer-img
@combos-fun/plugin-renderer-img
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@combos-fun/engine | AI (dependencies): Internal sibling dep within the same @combos-fun monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@combos-fun/plugin-renderer | AI (dependencies): Internal sibling dep within the same @combos-fun monorepo; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): New ecosystem package; no provenance is common and no other risk signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Early-stage scoped plugin package in a cohesive namespace; sparse metadata is expected at this stage. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.12 | 5 / 0 | |
| 0.0.11 | 5 / 0 | |
| 0.0.10 | 5 / 0 | |
| 0.0.9 | 5 / 0 | |
| 0.0.8 | 5 / 0 | |
| 0.0.7 | 5 / 0 | |
| 0.0.6 | 5 / 0 | |
| 0.0.5 | 5 / 0 | |
| 0.0.4 | 5 / 0 | |
| 0.0.3 | 5 / 0 | |
| 0.0.2 | 5 / 0 | |
| 0.0.1 | 5 / 0 |
v0.0.11
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.