@wix/bex-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/testkit/foldersStaticData.js | AI (source-diff): Long lines are static mock/testkit JSON data, not executable obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Internal Wix org roster churn under trusted wix-ci-publisher, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Internal Wix org roster churn under trusted wix-ci-publisher, not a takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix scoped package; missing metadata is expected for private monorepo artifacts. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher consistently publishes without provenance; stable pattern across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; no description is standard for Wix internal scoped packages. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 2.336.0 | 10 / 22 | |
| 2.333.0 | 10 / 22 | |
| 2.332.0 | 10 / 22 | |
| 2.331.0 | 10 / 22 | |
| 2.330.0 | 10 / 22 | |
| 2.329.0 | 10 / 22 | |
| 2.328.0 | 10 / 22 | |
| 2.327.0 | 10 / 22 | |
| 2.326.0 | 10 / 22 | |
| 2.325.0 | 10 / 22 | |
| 2.324.0 | 10 / 22 | |
| 2.323.0 | 10 / 22 | |
| 2.322.0 | 10 / 22 | |
| 2.321.0 | 10 / 22 | |
| 2.320.0 | 10 / 22 | |
| 2.319.0 | 10 / 22 | |
| 2.318.0 | 10 / 22 | |
| 2.317.0 | 10 / 22 | |
| 2.316.0 | 10 / 22 | |
| 2.315.0 | 10 / 22 | |
| 2.314.0 | 10 / 22 | |
| 2.313.0 | 10 / 22 | |
| 2.311.0 | 10 / 22 | |
| 2.310.0 | 10 / 22 | |
| 2.309.0 | 10 / 22 | |
| 2.308.0 | 10 / 22 | |
| 2.307.0 | 10 / 22 | |
| 2.306.0 | 10 / 22 | |
| 2.305.0 | 10 / 22 | |
| 2.303.0 | 10 / 22 | |
| 2.302.0 | 10 / 22 | |
| 2.301.0 | 10 / 22 | |
| 2.300.0 | 10 / 22 | |
| 2.299.0 | 10 / 22 | |
| 2.298.0 | 10 / 22 | |
| 2.297.0 | 10 / 22 | |
| 2.295.0 | 10 / 22 | |
| 2.294.0 | 10 / 22 | |
| 2.293.0 | 10 / 22 | |
| 2.292.0 | 10 / 22 | |
| 2.291.0 | 10 / 21 | |
| 2.290.0 | 10 / 21 | |
| 2.289.0 | 10 / 21 | |
| 2.288.0 | 10 / 21 | |
| 2.287.0 | 10 / 21 | |
| 2.284.0 | 10 / 21 | |
| 2.282.0 | 10 / 21 | |
| 2.279.0 | 10 / 21 | |
| 2.278.0 | 10 / 21 | |
| 2.277.0 | 9 / 20 | |
| 2.276.0 | 9 / 20 | |
| 2.275.0 | 9 / 20 | |
| 2.274.0 | 9 / 20 | |
| 2.273.0 | 9 / 20 | |
| 2.272.0 | 9 / 20 | |
| 2.271.0 | 9 / 20 | |
| 2.269.0 | 9 / 20 | |
| 2.266.0 | 9 / 20 | |
| 2.264.0 | 9 / 20 | |
| 2.262.0 | 9 / 20 | |
| 2.260.0 | 9 / 20 | |
| 2.258.0 | 9 / 20 | |
| 2.253.0 | 9 / 20 | |
| 2.252.0 | 9 / 20 | |
| 2.250.0 | 9 / 20 | |
| 2.249.0 | 9 / 20 | |
| 2.239.0 | 9 / 20 | |
| 2.235.0 | 9 / 20 | |
| 2.233.0 | 9 / 20 | |
| 2.20.0 | 8 / 19 | |
| 2.19.0 | 8 / 19 | |
| 2.18.0 | 8 / 19 | |
| 2.17.0 | 8 / 19 | |
| 2.16.0 | 8 / 19 | |
| 2.15.0 | 8 / 19 | |
| 2.14.0 | 8 / 19 | |
| 2.13.0 | 8 / 19 | |
| 2.12.0 | 8 / 19 | |
| 2.11.0 | 8 / 19 | |
| 2.10.0 | 8 / 19 | |
| 2.9.0 | 8 / 19 | |
| 2.8.0 | 8 / 19 | |
| 2.7.0 | 8 / 19 | |
| 2.6.0 | 8 / 19 | |
| 2.5.0 | 8 / 19 | |
| 2.4.0 | 8 / 19 | |
| 2.3.0 | 8 / 19 | |
| 2.2.0 | 8 / 19 | |
| 2.1.0 | 8 / 19 | |
| 2.0.0 | 8 / 19 |
v2.336.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.333.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.332.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.331.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.330.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.329.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.289.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.288.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.287.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.284.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.282.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.279.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.278.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.277.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.276.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.275.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.274.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.273.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.272.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.271.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.269.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.266.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.264.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.262.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.260.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.258.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.253.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.252.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.250.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.249.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.239.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.235.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.233.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.