@wix/patterns-fields
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal Wix monorepo package; missing metadata is expected for org-internal packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Wix package; missing description is consistent with org-internal tooling. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher consistently publishes without Sigstore provenance; stable pattern across 1681 approved packages. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Phantom dep heuristic; semver referenced in config files is a common false positive. | ai | |
| phantom-deps | phantom-dep:@wix/data | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on peer/config references in monorepos. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.44.0 | 19 / 24 | |
| 1.43.0 | 19 / 24 | |
| 1.42.0 | 19 / 24 | |
| 1.41.0 | 19 / 24 | |
| 1.40.0 | 19 / 24 | |
| 1.39.0 | 19 / 24 | |
| 1.38.0 | 19 / 23 | |
| 1.37.0 | 19 / 23 | |
| 1.36.0 | 18 / 24 | |
| 1.35.0 | 18 / 24 | |
| 1.33.0 | 17 / 24 | |
| 1.32.0 | 17 / 24 | |
| 1.30.0 | 17 / 24 | |
| 1.29.0 | 17 / 24 | |
| 1.28.0 | 17 / 24 | |
| 1.27.0 | 17 / 24 | |
| 1.26.0 | 17 / 24 | |
| 1.25.0 | 17 / 24 | |
| 1.10.0 | 17 / 24 | |
| 1.9.0 | 17 / 24 | |
| 1.8.0 | 17 / 24 | |
| 1.4.0 | 17 / 24 |
v1.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.