← Home

@jalvin/runtime

npm

Jalvin runtime — Bibi HTTP client, coroutines, StateFlow, ViewModel, UI hooks

47
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sixstringcal

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Package has no CI provenance setup; consistent across versions, not a malware signal. ai

Versions (showing 47 of 47)

Version Deps Published
2.0.50 0 / 5
2.0.49 0 / 5
2.0.48 0 / 5
2.0.47 0 / 5
2.0.45 0 / 4
2.0.43 0 / 4
2.0.42 0 / 4
2.0.40 0 / 4
2.0.39 0 / 4
2.0.36 0 / 5
2.0.35 0 / 5
2.0.34 0 / 5
2.0.33 0 / 5
2.0.32 0 / 5
2.0.31 0 / 5
2.0.30 0 / 5
2.0.29 0 / 5
2.0.28 0 / 5
2.0.27 0 / 5
2.0.26 0 / 5
2.0.25 0 / 5
2.0.24 0 / 5
2.0.23 0 / 5
2.0.22 0 / 5
2.0.21 0 / 5
2.0.20 0 / 5
2.0.19 0 / 5
2.0.18 0 / 5
2.0.17 0 / 5
2.0.16 0 / 5
2.0.15 0 / 5
2.0.14 0 / 5
2.0.13 0 / 5
2.0.12 0 / 5
2.0.11 0 / 5
2.0.10 0 / 5
2.0.9 0 / 5
2.0.8 0 / 5
2.0.7 0 / 5
2.0.6 0 / 5
2.0.5 0 / 5
2.0.4 0 / 5
2.0.3 0 / 5
2.0.2 0 / 3
2.0.1 0 / 3
2.0.0 0 / 3
1.0.0 0 / 3

v2.0.50

1 finding
INFO No provenance attestation provenance

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

v2.0.49

1 finding
INFO No provenance attestation provenance

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