@holochain-open-dev/signals
Holochain async-signals to build reusable holochain-open-dev modules
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@shoelace-style/shoelace | AI (phantom-deps): Shoelace is a UI component peer dep referenced in config/templates, not directly imported in JS — stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.601.0 | 6 / 5 | |
| 0.300.9 | 6 / 5 | |
| 0.300.8 | 6 / 5 | |
| 0.300.7 | 6 / 5 | |
| 0.300.6 | 6 / 5 | |
| 0.300.5 | 6 / 5 | |
| 0.300.4 | 6 / 5 | |
| 0.300.3 | 6 / 5 | |
| 0.300.2 | 6 / 5 | |
| 0.300.1 | 6 / 5 | |
| 0.300.0 | 6 / 5 |
v0.300.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.300.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.300.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.