@wix/benefit-programs
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
Keywords
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): Wix auto-generated SDK packages intentionally lack descriptions/repo URLs; templated naming is by design across the Wix SDK ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix internal SDK package; missing description is a consistent pattern across this publisher's packages, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher consistently publishes without Sigstore provenance; stable pattern across 2005 approved packages. | ai |
Versions (showing 28 of 135)
| Version | Deps | Published |
|---|---|---|
| 1.0.125 | 7 / 2 | |
| 1.0.124 | 7 / 2 | |
| 1.0.123 | 7 / 2 | |
| 1.0.122 | 7 / 2 | |
| 1.0.121 | 7 / 2 | |
| 1.0.120 | 7 / 2 | |
| 1.0.119 | 7 / 2 | |
| 1.0.118 | 7 / 2 | |
| 1.0.117 | 7 / 1 | |
| 1.0.116 | 7 / 1 | |
| 1.0.115 | 7 / 1 | |
| 1.0.114 | 7 / 1 | |
| 1.0.113 | 7 / 1 | |
| 1.0.112 | 7 / 1 | |
| 1.0.111 | 7 / 1 | |
| 1.0.110 | 7 / 1 | |
| 1.0.109 | 7 / 1 | |
| 1.0.108 | 7 / 2 | |
| 1.0.107 | 7 / 2 | |
| 1.0.106 | 7 / 2 | |
| 1.0.105 | 7 / 2 | |
| 1.0.104 | 7 / 2 | |
| 1.0.103 | 7 / 2 | |
| 1.0.102 | 7 / 1 | |
| 1.0.101 | 7 / 1 | |
| 1.0.100 | 7 / 1 | |
| 1.0.99 | 7 / 1 | |
| 1.0.98 | 7 / 1 |
v1.0.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.