@wix/patterns-fields-utils
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Wix internal package; maintainer additions within the Wix org are routine and low-risk given the CI publisher track record. | ai | |
| dependencies | unvetted-dep:path-parse | AI (dependencies): path-parse is a well-known utility; phantom-dep finding suggests it may be a transitive/bundled dep rather than directly used. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix monorepo package; missing metadata is expected for private/scoped packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Wix package; missing description is a known pattern for this publisher's packages. | ai | |
| phantom-deps | phantom-dep:path-parse | AI (phantom-deps): Likely used in build scripts or bundled modules rather than direct imports. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped package loaded by convention via Babel transform, not direct import. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.25.0 | 7 / 8 | |
| 1.24.0 | 7 / 8 | |
| 1.23.0 | 7 / 8 | |
| 1.22.0 | 7 / 8 | |
| 1.21.0 | 7 / 8 | |
| 1.20.0 | 7 / 8 | |
| 1.19.0 | 7 / 8 | |
| 1.18.0 | 7 / 8 | |
| 1.17.0 | 7 / 8 | |
| 1.16.0 | 7 / 8 | |
| 1.15.0 | 7 / 8 | |
| 1.14.0 | 7 / 8 | |
| 1.13.0 | 7 / 8 | |
| 1.12.0 | 7 / 8 | |
| 1.11.0 | 7 / 8 | |
| 1.10.0 | 7 / 8 | |
| 1.9.0 | 7 / 8 | |
| 1.8.0 | 7 / 8 | |
| 1.7.0 | 7 / 8 | |
| 1.6.0 | 7 / 8 |
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.