@ws-ui/store
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:minimatch | AI (phantom-deps): Monorepo config-file usage; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-icons | AI (phantom-deps): Likely referenced in config/barrel files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ws-ui/icons | AI (phantom-deps): Same-org scope; overrides block shows intentional peer resolution, not phantom usage. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.13.3 | 11 / 17 | |
| 1.13.2 | 11 / 17 | |
| 1.13.1 | 11 / 17 | |
| 1.13.0 | 11 / 17 | |
| 1.12.4 | 11 / 17 | |
| 1.12.3 | 11 / 17 | |
| 1.12.1 | 11 / 17 | |
| 1.6.8 | 11 / 17 | |
| 1.6.7 | 11 / 17 | |
| 1.6.6 | 11 / 17 | |
| 1.6.5 | 11 / 17 | |
| 1.6.3 | 11 / 17 | |
| 1.6.2 | 11 / 17 | |
| 1.6.1 | 11 / 17 | |
| 1.6.0 | 11 / 17 | |
| 1.5.15 | 11 / 17 | |
| 1.5.14 | 11 / 17 | |
| 1.5.13 | 11 / 17 | |
| 1.5.12 | 11 / 17 | |
| 1.5.11 | 11 / 17 | |
| 1.5.10 | 11 / 17 | |
| 1.5.9 | 11 / 17 | |
| 1.5.8 | 11 / 17 | |
| 1.5.7 | 2 / 23 | |
| 1.5.6 | 2 / 23 | |
| 1.5.5 | 2 / 23 | |
| 1.5.4 | 2 / 23 | |
| 1.5.3 | 2 / 23 |
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
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 2026-04-29, 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.
v1.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.