@node-projects/web-component-designer-visualization-addons
web-component-designer addon for visualizations
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 138 versions; no provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:@blockly/zoom-to-fit | AI (phantom-deps): Declared dep used as an esbuild external; not directly imported in source but legitimately referenced. | ai |
Versions (showing 15 of 115)
| Version | Deps | Published |
|---|---|---|
| 0.1.40 | 10 / 0 | |
| 0.1.39 | 10 / 0 | |
| 0.1.38 | 10 / 0 | |
| 0.1.37 | 10 / 0 | |
| 0.1.36 | 10 / 0 | |
| 0.1.35 | 10 / 0 | |
| 0.1.34 | 10 / 0 | |
| 0.1.33 | 10 / 0 | |
| 0.1.32 | 10 / 0 | |
| 0.1.31 | 10 / 0 | |
| 0.1.30 | 10 / 0 | |
| 0.1.29 | 10 / 0 | |
| 0.1.28 | 9 / 0 | |
| 0.1.27 | 9 / 0 | |
| 0.1.26 | 9 / 0 |
v0.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.