← Home

@combos-fun/plugin-renderer-render

npm

@combos-fun/plugin-renderer-render

12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sun668

Keywords

combos-funvisibilityalphaz-indexsortable2d

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:pixi.js AI (phantom-deps): pixi.js is a peer/transitive dep used indirectly via renderer-adapter; phantom-dep false positive for this package. ai
phantom-deps phantom-dep:@combos-fun/renderer-adapter AI (phantom-deps): Same-org adapter dep; likely used indirectly through plugin-renderer. Stable false positive for this monorepo package. 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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.