← Home

@esfaenza/es-diagrams

28
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

energysoftwarefaenza

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Long-lived scoped package with consistent history; missing metadata is a quality issue, not a security signal. ai
npm-metadata no-description AI (npm-metadata): Stable package with 107 versions; absent description is cosmetic. ai
provenance no-provenance AI (provenance): No provenance is common; no other risk signals present. ai

Versions (showing 28 of 28)

Version Deps Published
20.3.5 1 / 0
20.3.4 1 / 0
20.3.3 1 / 0
20.3.2 1 / 0
20.3.1 1 / 0
20.3.0 1 / 0
19.2.28 1 / 0
19.2.27 1 / 0
19.2.24 1 / 0
19.2.23 1 / 0
19.2.22 1 / 0
19.2.21 1 / 0
19.2.15 1 / 0
19.2.14 1 / 0
19.2.13 1 / 0
19.2.12 1 / 0
19.2.11 1 / 0
19.2.10 1 / 0
19.2.9 1 / 0
19.2.8 1 / 0
19.2.7 1 / 0
19.2.6 1 / 0
19.2.5 1 / 0
19.2.4 1 / 0
19.2.3 1 / 0
19.2.2 1 / 0
19.2.1 1 / 0
19.2.0 1 / 0

v20.3.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.