@ws-ui/craftjs-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:debounce | AI (phantom-deps): debounce is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.2.26 | 4 / 4 | |
| 0.2.25 | 4 / 4 | |
| 0.2.24 | 4 / 4 | |
| 0.2.23 | 4 / 4 | |
| 0.2.22 | 4 / 4 | |
| 0.2.21 | 4 / 4 | |
| 0.2.20 | 4 / 4 | |
| 0.2.19 | 4 / 4 | |
| 0.2.18 | 4 / 4 | |
| 0.2.17 | 4 / 4 | |
| 0.2.16 | 4 / 4 | |
| 0.2.15 | 4 / 4 | |
| 0.2.14 | 4 / 3 | |
| 0.2.13 | 4 / 3 | |
| 0.2.12 | 4 / 3 | |
| 0.2.11 | 4 / 3 | |
| 0.2.10 | 4 / 3 | |
| 0.2.9 | 4 / 3 | |
| 0.2.8 | 4 / 3 | |
| 0.2.7 | 4 / 3 | |
| 0.2.6 | 4 / 3 |
v0.2.25
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2024-12-26, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.24
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (axel-dev) than the most recent previously approved version (idrissi) on 2024-12-03, but axel-dev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2024-10-31, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.15
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (axel-dev) than the most recent previously approved version (idrissi) on 2024-10-24, but axel-dev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2024-09-10, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2024-09-10, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (axel-dev) than the most recent previously approved version (idrissi) on 2024-08-10, but axel-dev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2024-06-06, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (axel-dev) than the most recent previously approved version (anass00) on 2024-06-05, but axel-dev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.