@wix/comments
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 consistently lack descriptions/repo URLs and share templated names; not a malice indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK modules routinely omit descriptions; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI pipeline does not attach Sigstore provenance; consistent across all Wix SDK packages. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_comments_ratings | AI (dependencies): Internal Wix auto-generated SDK dep; stable pattern across this package family. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_comments_categories | AI (dependencies): Internal Wix auto-generated SDK dep; stable pattern across this package family. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_comments_widgets | AI (dependencies): Internal Wix auto-generated SDK dep; stable pattern across this package family. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_comments_comments | AI (dependencies): Internal Wix auto-generated SDK dep; stable pattern across this package family. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 1.0.184 | 4 / 2 | |
| 1.0.183 | 4 / 2 | |
| 1.0.182 | 4 / 2 | |
| 1.0.181 | 4 / 2 | |
| 1.0.180 | 4 / 2 | |
| 1.0.179 | 4 / 2 | |
| 1.0.178 | 4 / 2 | |
| 1.0.177 | 4 / 2 | |
| 1.0.176 | 4 / 2 | |
| 1.0.175 | 3 / 2 | |
| 1.0.174 | 3 / 2 | |
| 1.0.173 | 3 / 2 | |
| 1.0.172 | 3 / 2 | |
| 1.0.171 | 3 / 2 | |
| 1.0.170 | 3 / 2 | |
| 1.0.169 | 3 / 2 | |
| 1.0.168 | 3 / 2 | |
| 1.0.167 | 3 / 2 | |
| 1.0.166 | 3 / 2 | |
| 1.0.165 | 3 / 2 | |
| 1.0.164 | 3 / 2 | |
| 1.0.163 | 3 / 2 | |
| 1.0.162 | 3 / 2 | |
| 1.0.161 | 3 / 2 | |
| 1.0.160 | 3 / 2 | |
| 1.0.159 | 3 / 2 | |
| 1.0.158 | 3 / 2 | |
| 1.0.157 | 3 / 2 | |
| 1.0.156 | 3 / 2 | |
| 1.0.155 | 3 / 2 | |
| 1.0.154 | 3 / 2 | |
| 1.0.153 | 3 / 2 | |
| 1.0.152 | 3 / 2 | |
| 1.0.151 | 3 / 2 | |
| 1.0.150 | 3 / 2 | |
| 1.0.148 | 3 / 2 | |
| 1.0.147 | 3 / 2 | |
| 1.0.146 | 3 / 2 | |
| 1.0.145 | 3 / 2 | |
| 1.0.144 | 3 / 2 | |
| 1.0.143 | 3 / 2 | |
| 1.0.142 | 3 / 2 | |
| 1.0.141 | 3 / 2 | |
| 1.0.140 | 3 / 2 | |
| 1.0.139 | 3 / 2 | |
| 1.0.138 | 3 / 2 | |
| 1.0.137 | 3 / 2 | |
| 1.0.136 | 3 / 2 | |
| 1.0.135 | 3 / 2 | |
| 1.0.134 | 3 / 2 | |
| 1.0.133 | 3 / 2 |
v1.0.184
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.183
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.181
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.177
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.176
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.174
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.172
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.171
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.170
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.160
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.159
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.158
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.157
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.156
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.152
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.