← Home

@leafer-ui/draw

npm Repository Homepage
36
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

leaferjs

Keywords

leafer drawleafer-uileaferjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Part of a large established monorepo; sparse README is a style choice, not spam. ai
provenance no-provenance AI (provenance): Publisher has 280 approved packages; lack of provenance is consistent across the ecosystem and not a risk signal here. ai

Versions (showing 36 of 36)

Version Deps Published
2.2.5 5 / 0
2.2.4 5 / 0
2.2.3 5 / 0
2.2.2 5 / 0
2.2.1 5 / 0
2.2.0 5 / 0
2.1.11 5 / 0
2.1.10 5 / 0
2.1.9 5 / 0
2.1.8 5 / 0
2.1.7 5 / 0
2.1.6 5 / 0
2.1.5 5 / 0
2.1.4 5 / 0
2.1.3 5 / 0
2.1.2 5 / 0
2.1.1 5 / 0
2.1.0 5 / 0
2.0.9 5 / 0
2.0.8 5 / 0
2.0.7 5 / 0
2.0.6 5 / 0
2.0.5 5 / 0
2.0.4 5 / 0
2.0.3 5 / 0
2.0.2 5 / 0
2.0.1 5 / 0
2.0.0 5 / 0
1.12.4 5 / 0
1.12.3 5 / 0
1.12.2 5 / 0
1.12.1 5 / 0
1.12.0 5 / 0
1.11.2 5 / 0
1.11.1 5 / 0
1.11.0 5 / 0

v2.2.5

1 finding
INFO No provenance attestation provenance

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

v2.2.4

1 finding
INFO No provenance attestation provenance

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

v2.2.3

1 finding
INFO No provenance attestation provenance

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

v2.2.2

1 finding
INFO No provenance attestation provenance

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

v2.2.1

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
INFO No provenance attestation provenance

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

v2.1.11

1 finding
INFO No provenance attestation provenance

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

v2.1.10

1 finding
INFO No provenance attestation provenance

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

v2.1.9

1 finding
INFO No provenance attestation provenance

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