← Home

@firestitch/diagram

5
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

wis-nzhornraygigbastersmendorjurymukhamikepatersonarioshaman

Keywords

angular

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@jsplumb/browser-ui AI (dependencies): @jsplumb/browser-ui is the official jsPlumb diagramming library; expected dependency for this package. ai
npm-metadata no-description AI (npm-metadata): Compiled Angular library package; missing description is a build artifact pattern, not a malware signal. ai
provenance no-provenance AI (provenance): Established Firestitch package; no provenance is consistent across their published versions. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known Angular compiler implicit dependency; stable false positive for this package. ai

Versions (showing 5 of 5)

Version Deps Published
18.0.20 2 / 0
18.0.19 2 / 0
18.0.18 2 / 0
18.0.17 2 / 0
18.0.16 2 / 0

v18.0.20

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.

v18.0.19

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.

v18.0.18

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.

v18.0.17

1 finding
INFO No provenance attestation provenance

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

v18.0.16

1 finding
INFO No provenance attestation provenance

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