@wix/error-handler
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Published by trusted Wix CI publisher with clean track record; dormancy consistent with org restructuring. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix monorepo package; missing metadata (repo, keywords, README) is expected for scoped internal packages published via wix-ci-publisher. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.68.0 | 5 / 32 | |
| 1.67.0 | 5 / 33 | |
| 1.66.0 | 5 / 33 | |
| 1.65.0 | 5 / 33 | |
| 1.64.0 | 5 / 33 | |
| 1.63.0 | 5 / 32 | |
| 1.62.0 | 5 / 32 | |
| 1.61.0 | 5 / 32 | |
| 1.60.0 | 5 / 32 | |
| 1.59.0 | 5 / 29 | |
| 1.58.0 | 5 / 29 | |
| 1.57.0 | 5 / 29 | |
| 1.56.0 | 5 / 28 | |
| 1.55.0 | 5 / 28 | |
| 1.54.0 | 5 / 28 | |
| 1.53.0 | 5 / 28 | |
| 1.52.0 | 5 / 28 | |
| 1.51.0 | 5 / 28 | |
| 1.50.0 | 5 / 28 | |
| 1.49.0 | 5 / 28 | |
| 1.48.0 | 5 / 28 | |
| 1.47.0 | 5 / 28 | |
| 1.46.0 | 5 / 28 | |
| 1.45.0 | 5 / 28 | |
| 1.44.0 | 5 / 28 | |
| 1.43.0 | 5 / 27 |
v1.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.