@wooksjs/event-core
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
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.7.21 | 0 / 2 | |
| 0.7.20 | 0 / 2 | |
| 0.7.19 | 0 / 2 | |
| 0.7.18 | 0 / 2 | |
| 0.7.17 | 0 / 2 | |
| 0.7.16 | 0 / 2 | |
| 0.7.15 | 0 / 2 | |
| 0.7.14 | 0 / 2 | |
| 0.7.13 | 0 / 2 | |
| 0.7.12 | 0 / 2 | |
| 0.7.11 | 0 / 2 | |
| 0.7.10 | 0 / 2 | |
| 0.7.9 | 0 / 2 | |
| 0.7.8 | 0 / 2 | |
| 0.7.7 | 0 / 2 | |
| 0.7.6 | 0 / 2 | |
| 0.7.5 | 0 / 2 | |
| 0.7.4 | 0 / 2 | |
| 0.7.3 | 0 / 2 | |
| 0.7.2 | 0 / 2 | |
| 0.7.1 | 0 / 2 | |
| 0.7.0 | 0 / 2 | |
| 0.6.6 | 1 / 2 | |
| 0.6.5 | 1 / 2 | |
| 0.6.4 | 1 / 2 | |
| 0.6.3 | 1 / 2 | |
| 0.6.2 | 1 / 2 | |
| 0.6.1 | 1 / 2 | |
| 0.5.20 | 2 / 0 | |
| 0.5.19 | 2 / 0 | |
| 0.5.18 | 2 / 0 | |
| 0.5.17 | 2 / 0 | |
| 0.5.16 | 2 / 0 | |
| 0.5.15 | 2 / 0 | |
| 0.5.14 | 2 / 0 | |
| 0.5.13 | 2 / 0 | |
| 0.5.12 | 2 / 0 | |
| 0.5.11 | 2 / 0 | |
| 0.5.10 | 2 / 0 | |
| 0.5.9 | 2 / 0 | |
| 0.5.8 | 2 / 0 | |
| 0.5.7 | 2 / 0 | |
| 0.5.6 | 2 / 0 | |
| 0.5.5 | 2 / 0 | |
| 0.5.4 | 2 / 0 | |
| 0.5.3 | 2 / 0 | |
| 0.5.2 | 2 / 0 | |
| 0.5.1 | 2 / 0 | |
| 0.5.0 | 2 / 0 | |
| 0.4.37 | 2 / 0 | |
| 0.4.36 | 2 / 0 |
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.