← Home

@luomus/laji-validate

Declarative validations for JavaScript

11
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

olzraitimjlummemerannisblodirrpulkka

Keywords

validationvalidateserverclient

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:geojson-bounds AI (dependencies): Stable dependency present across prior versions; no malware indicators. ai
dependencies unvetted-dep:@luomus/laji-map AI (dependencies): Same-org dependency, present across prior versions; no malware indicators. ai
dependencies unvetted-dep:@luomus/validate AI (dependencies): Same-org dependency, present across prior versions; no malware indicators. ai
provenance no-provenance AI (provenance): Org-published package on Bitbucket; provenance attestation not expected for this publisher. ai

Versions (showing 11 of 11)

Version Deps Published
0.0.133 6 / 18
0.0.132 6 / 18
0.0.131 6 / 18
0.0.130 6 / 18
0.0.129 6 / 18
0.0.127 6 / 18
0.0.126 6 / 18
0.0.125 6 / 18
0.0.124 6 / 18
0.0.123 6 / 18
0.0.122 6 / 18

v0.0.122

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.