@wix/patterns
Patterns is a React library with advanced components that extend the functionality of the core components from the [Wix Design System](https://www.wixdesignsystem.com/). It provides fully-featured sophisticated experiences tailored for common functionalit
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:tslib | AI (phantom-deps): tslib is a well-known implicit runtime dep for TypeScript-compiled packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types referenced in config files is a common pattern for React component libraries; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-modal | AI (phantom-deps): Referenced in config files only; consistent with UI component library patterns. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.417.0 | 24 / 76 | |
| 1.416.0 | 24 / 76 | |
| 1.415.0 | 24 / 76 | |
| 1.414.0 | 24 / 76 | |
| 1.413.0 | 24 / 76 | |
| 1.412.0 | 24 / 76 | |
| 1.411.0 | 24 / 76 | |
| 1.410.0 | 24 / 76 | |
| 1.409.0 | 24 / 76 | |
| 1.408.0 | 24 / 76 | |
| 1.407.0 | 24 / 76 | |
| 1.405.0 | 24 / 75 | |
| 1.404.0 | 24 / 75 | |
| 1.403.0 | 24 / 75 | |
| 1.399.0 | 24 / 75 | |
| 1.398.0 | 24 / 75 | |
| 1.395.0 | 24 / 75 | |
| 1.392.0 | 24 / 75 | |
| 1.390.0 | 24 / 75 |
v1.417.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.416.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.415.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.414.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.413.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.412.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.411.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.410.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.409.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.408.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.407.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.405.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.404.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.403.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.399.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.398.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.395.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.392.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.390.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.