@wocker/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @wocker/core is part of the Wocker project ecosystem, not a typosquat of cors. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user project config file (wocker.config.js) from known path — standard config-loading pattern. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 7 / 11 | |
| 1.1.2 | 7 / 11 | |
| 1.1.1 | 7 / 11 | |
| 1.1.0 | 7 / 11 | |
| 1.0.32 | 6 / 11 | |
| 1.0.31 | 6 / 11 | |
| 1.0.30 | 6 / 11 | |
| 1.0.29 | 6 / 11 | |
| 1.0.28 | 6 / 11 | |
| 1.0.27 | 6 / 11 | |
| 1.0.26 | 6 / 11 | |
| 1.0.25 | 9 / 11 | |
| 1.0.24 | 8 / 11 | |
| 1.0.23 | 7 / 11 | |
| 1.0.22 | 4 / 9 | |
| 1.0.21 | 4 / 7 | |
| 1.0.20 | 4 / 7 | |
| 1.0.19 | 4 / 7 | |
| 1.0.18 | 4 / 7 | |
| 1.0.17 | 4 / 7 | |
| 1.0.16 | 4 / 7 | |
| 1.0.15 | 4 / 7 | |
| 1.0.14 | 4 / 7 | |
| 1.0.13 | 4 / 7 | |
| 1.0.12 | 4 / 7 | |
| 1.0.11 | 4 / 7 |
v1.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.