← Home

@combos-fun/plugin-renderer-nine-patch

npm

@combos-fun/plugin-renderer-nine-patch

32
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

sun668

Keywords

combos-funnine-patchnine-slicepaneluistretch2d

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@combos-fun/engine AI (dependencies): Same-org monorepo dependency; consistent versioning pattern across all @combos-fun/* packages. ai
dependencies unvetted-dep:@combos-fun/plugin-renderer AI (dependencies): Same-org monorepo dependency; consistent versioning pattern across all @combos-fun/* packages. ai
provenance no-provenance AI (provenance): New package from a small game engine project; provenance absence is common and not a risk signal here. ai
bogus-package bogus-package AI (bogus-package): Early-stage monorepo plugin; sparse metadata is expected for a new game engine ecosystem, not spam. ai

Versions (showing 32 of 32)

Version Deps Published
0.0.34 5 / 0
0.0.33 5 / 0
0.0.32 5 / 0
0.0.31 5 / 0
0.0.30 5 / 0
0.0.29 5 / 0
0.0.28 5 / 0
0.0.27 5 / 0
0.0.24 5 / 0
0.0.23 5 / 0
0.0.22 5 / 0
0.0.21 5 / 0
0.0.20 5 / 0
0.0.19 5 / 0
0.0.18 5 / 0
0.0.17 5 / 0
0.0.16 5 / 0
0.0.15 5 / 0
0.0.14 5 / 0
0.0.13 5 / 0
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.34

1 finding
INFO No provenance attestation provenance

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

v0.0.33

1 finding
INFO No provenance attestation provenance

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

v0.0.32

1 finding
INFO No provenance attestation provenance

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

v0.0.31

1 finding
INFO No provenance attestation provenance

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

v0.0.30

1 finding
INFO No provenance attestation provenance

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

v0.0.29

1 finding
INFO No provenance attestation provenance

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

v0.0.28

1 finding
INFO No provenance attestation provenance

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

v0.0.27

1 finding
INFO No provenance attestation provenance

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

v0.0.24

1 finding
INFO No provenance attestation provenance

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

v0.0.23

1 finding
INFO No provenance attestation provenance

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

v0.0.22

1 finding
INFO No provenance attestation provenance

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

v0.0.21

1 finding
INFO No provenance attestation provenance

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

v0.0.20

1 finding
INFO No provenance attestation provenance

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

v0.0.19

1 finding
INFO No provenance attestation provenance

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

v0.0.18

1 finding
INFO No provenance attestation provenance

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

v0.0.17

1 finding
INFO No provenance attestation provenance

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

v0.0.16

1 finding
INFO No provenance attestation provenance

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

v0.0.15

1 finding
INFO No provenance attestation provenance

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

v0.0.14

1 finding
INFO No provenance attestation provenance

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

v0.0.13

1 finding
INFO No provenance attestation provenance

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