@firestitch/diagram
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 21 of 21)
| 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 | |
| 18.0.15 | 3 / 0 | |
| 18.0.14 | 3 / 0 | |
| 18.0.13 | 3 / 0 | |
| 18.0.12 | 3 / 0 | |
| 18.0.11 | 3 / 0 | |
| 18.0.10 | 3 / 0 | |
| 18.0.9 | 3 / 0 | |
| 18.0.8 | 3 / 0 | |
| 18.0.7 | 3 / 0 | |
| 18.0.6 | 3 / 0 | |
| 18.0.5 | 3 / 0 | |
| 18.0.4 | 3 / 0 | |
| 18.0.3 | 3 / 0 | |
| 18.0.2 | 3 / 0 | |
| 18.0.1 | 3 / 0 | |
| 18.0.0 | 3 / 0 |
v18.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.