moost
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:wooks | AI (dependencies): wooks is a first-party ecosystem dep from the same moostjs/wooksjs author; stable dependency across versions. | ai | |
| dependencies | unvetted-dep:@prostojs/mate | AI (dependencies): @prostojs/mate is a first-party prostojs dep from the same author; stable dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with consistent publish history; provenance not used by this publisher across versions. | ai |
Versions (showing 88 of 88)
| Version | Deps | Published |
|---|---|---|
| 0.6.34 | 6 / 4 | |
| 0.6.33 | 6 / 4 | |
| 0.6.32 | 6 / 4 | |
| 0.6.31 | 6 / 4 | |
| 0.6.30 | 6 / 4 | |
| 0.6.29 | 6 / 4 | |
| 0.6.28 | 6 / 4 | |
| 0.6.27 | 6 / 4 | |
| 0.6.26 | 6 / 4 | |
| 0.6.25 | 6 / 4 | |
| 0.6.24 | 6 / 4 | |
| 0.6.23 | 6 / 4 | |
| 0.6.22 | 6 / 4 | |
| 0.6.21 | 6 / 4 | |
| 0.6.20 | 6 / 4 | |
| 0.6.18 | 6 / 4 | |
| 0.6.17 | 6 / 4 | |
| 0.6.16 | 6 / 4 | |
| 0.6.15 | 6 / 4 | |
| 0.6.14 | 6 / 4 | |
| 0.6.13 | 6 / 4 | |
| 0.6.12 | 6 / 4 | |
| 0.6.10 | 6 / 4 | |
| 0.6.9 | 6 / 4 | |
| 0.6.8 | 6 / 4 | |
| 0.6.7 | 6 / 4 | |
| 0.6.6 | 6 / 4 | |
| 0.6.5 | 6 / 4 | |
| 0.6.4 | 6 / 4 | |
| 0.6.3 | 6 / 4 | |
| 0.6.2 | 6 / 4 | |
| 0.6.1 | 6 / 4 | |
| 0.6.0 | 6 / 4 | |
| 0.5.33 | 6 / 4 | |
| 0.5.32 | 6 / 4 | |
| 0.5.31 | 6 / 4 | |
| 0.5.30 | 6 / 4 | |
| 0.5.21 | 6 / 0 | |
| 0.5.20 | 6 / 0 | |
| 0.5.19 | 6 / 0 | |
| 0.5.18 | 6 / 0 | |
| 0.5.17 | 6 / 0 | |
| 0.5.16 | 6 / 0 | |
| 0.5.15 | 6 / 0 | |
| 0.5.14 | 6 / 0 | |
| 0.5.12 | 6 / 0 | |
| 0.5.11 | 6 / 0 | |
| 0.5.10 | 6 / 0 | |
| 0.5.9 | 6 / 0 | |
| 0.5.8 | 6 / 0 | |
| 0.5.7 | 6 / 0 | |
| 0.5.6 | 6 / 0 | |
| 0.5.5 | 6 / 0 | |
| 0.5.4 | 6 / 0 | |
| 0.5.3 | 6 / 0 | |
| 0.5.2 | 6 / 0 | |
| 0.5.1 | 6 / 0 | |
| 0.5.0 | 6 / 0 | |
| 0.4.23 | 6 / 0 | |
| 0.4.22 | 6 / 0 | |
| 0.4.21 | 6 / 0 | |
| 0.4.20 | 6 / 0 | |
| 0.4.19 | 6 / 0 | |
| 0.4.18 | 6 / 0 | |
| 0.4.17 | 6 / 0 | |
| 0.4.16 | 6 / 0 | |
| 0.4.15 | 6 / 0 | |
| 0.4.14 | 6 / 0 | |
| 0.4.13 | 6 / 0 | |
| 0.4.12 | 6 / 0 | |
| 0.4.11 | 6 / 0 | |
| 0.4.10 | 6 / 0 | |
| 0.4.9 | 6 / 0 | |
| 0.4.8 | 6 / 0 | |
| 0.4.7 | 6 / 0 | |
| 0.4.6 | 6 / 0 | |
| 0.4.5 | 6 / 0 | |
| 0.4.4 | 6 / 0 | |
| 0.4.3 | 6 / 0 | |
| 0.4.2 | 6 / 0 | |
| 0.4.1 | 6 / 0 | |
| 0.4.0 | 6 / 0 | |
| 0.3.44 | 5 / 0 | |
| 0.3.43 | 5 / 0 | |
| 0.3.42 | 5 / 0 | |
| 0.3.41 | 5 / 0 | |
| 0.3.40 | 5 / 0 | |
| 0.3.39 | 5 / 0 |
v0.6.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.