← Home

@holo-js/events

npm

Holo-JS Framework - event contracts and runtime surface

26
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

mmelouk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Lack of provenance is common across npm; no other risk signals present to elevate this finding for this package. ai

Versions (showing 26 of 26)

Version Deps Published
0.3.8 1 / 5
0.3.7 1 / 5
0.3.6 1 / 5
0.3.5 1 / 5
0.3.4 1 / 5
0.3.3 1 / 5
0.3.2 1 / 5
0.3.1 1 / 5
0.3.0 1 / 5
0.2.6 1 / 5
0.2.5 1 / 5
0.2.4 1 / 5
0.2.3 1 / 5
0.2.2 1 / 5
0.2.1 1 / 5
0.2.0 1 / 5
0.1.9 1 / 5
0.1.8 1 / 5
0.1.7 1 / 5
0.1.6 1 / 5
0.1.5 1 / 5
0.1.4 1 / 4
0.1.3 1 / 4
0.1.2 2 / 4
0.1.1 2 / 4
0.1.0 2 / 4

v0.3.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.