@signaltree/events
Event-driven architecture infrastructure for SignalTree - event bus, subscribers, validation, and real-time sync
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package has no provenance attestation but no other risk signals; acceptable for this package. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 13.1.0 | 0 / 11 | |
| 13.0.1 | 0 / 11 | |
| 13.0.0 | 0 / 11 | |
| 12.1.0 | 0 / 11 | |
| 12.0.0 | 0 / 11 | |
| 11.6.0 | 0 / 11 | |
| 11.5.3 | 0 / 11 | |
| 11.5.2 | 0 / 11 | |
| 11.5.1 | 0 / 11 | |
| 11.5.0 | 0 / 11 | |
| 11.4.1 | 0 / 11 | |
| 11.4.0 | 0 / 11 | |
| 11.3.0 | 0 / 11 | |
| 11.2.0 | 0 / 11 | |
| 11.1.1 | 0 / 11 | |
| 11.1.0 | 0 / 11 | |
| 11.0.3 | 0 / 11 | |
| 11.0.2 | 0 / 11 | |
| 11.0.1 | 0 / 11 | |
| 11.0.0 | 0 / 11 | |
| 10.6.0 | 0 / 11 | |
| 10.5.0 | 0 / 11 | |
| 10.4.1 | 0 / 11 | |
| 10.4.0 | 0 / 11 | |
| 10.3.3 | 0 / 11 | |
| 10.3.2 | 0 / 11 | |
| 10.3.1 | 0 / 11 | |
| 10.3.0 | 0 / 11 | |
| 10.2.0 | 0 / 11 | |
| 10.1.0 | 0 / 11 | |
| 10.0.0 | 0 / 11 | |
| 9.6.0 | 0 / 11 | |
| 9.5.2 | 0 / 11 | |
| 9.5.1 | 0 / 11 | |
| 9.5.0 | 0 / 11 | |
| 9.4.0 | 0 / 11 | |
| 9.3.0 | 0 / 11 | |
| 9.2.2 | 0 / 11 | |
| 9.2.1 | 0 / 11 | |
| 9.2.0 | 0 / 11 | |
| 9.1.0 | 0 / 11 | |
| 9.0.1 | 0 / 11 | |
| 9.0.0 | 0 / 11 | |
| 8.0.2 | 0 / 11 | |
| 8.0.1 | 0 / 11 | |
| 8.0.0 | 0 / 11 | |
| 7.6.1 | 0 / 11 | |
| 7.6.0 | 0 / 11 | |
| 7.5.5 | 0 / 11 | |
| 7.5.4 | 0 / 11 | |
| 7.5.3 | 0 / 11 |
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.