@wix/wix-data-items-common
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/kind-of | AI (phantom-deps): @types/kind-of is a type declaration package used at compile time; not directly imported at runtime is expected. | ai | |
| phantom-deps | phantom-dep:@types/safe-json-stringify | AI (phantom-deps): @types/safe-json-stringify is a type declaration package used at compile time; not directly imported at runtime is expected. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix scoped package; missing metadata signals are expected for private org packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Wix package; missing description is consistent across the org's internal libraries. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 100 of 153)
| Version | Deps | Published |
|---|---|---|
| 1.0.323 | 3 / 8 | |
| 1.0.322 | 3 / 8 | |
| 1.0.321 | 3 / 8 | |
| 1.0.320 | 3 / 8 | |
| 1.0.319 | 3 / 8 | |
| 1.0.318 | 3 / 8 | |
| 1.0.317 | 3 / 8 | |
| 1.0.316 | 3 / 8 | |
| 1.0.315 | 3 / 8 | |
| 1.0.314 | 3 / 8 | |
| 1.0.313 | 3 / 8 | |
| 1.0.312 | 3 / 8 | |
| 1.0.311 | 3 / 8 | |
| 1.0.310 | 3 / 8 | |
| 1.0.309 | 3 / 8 | |
| 1.0.308 | 3 / 8 | |
| 1.0.307 | 3 / 8 | |
| 1.0.306 | 3 / 8 | |
| 1.0.305 | 3 / 8 | |
| 1.0.304 | 3 / 8 | |
| 1.0.303 | 3 / 8 | |
| 1.0.302 | 3 / 8 | |
| 1.0.301 | 3 / 8 | |
| 1.0.300 | 3 / 8 | |
| 1.0.299 | 3 / 8 | |
| 1.0.298 | 3 / 8 | |
| 1.0.297 | 3 / 8 | |
| 1.0.296 | 3 / 8 | |
| 1.0.295 | 3 / 8 | |
| 1.0.294 | 3 / 8 | |
| 1.0.293 | 3 / 8 | |
| 1.0.292 | 3 / 8 | |
| 1.0.291 | 3 / 8 | |
| 1.0.290 | 3 / 8 | |
| 1.0.289 | 3 / 8 | |
| 1.0.288 | 3 / 8 | |
| 1.0.287 | 3 / 8 | |
| 1.0.286 | 3 / 8 | |
| 1.0.285 | 3 / 8 | |
| 1.0.284 | 3 / 8 | |
| 1.0.283 | 3 / 8 | |
| 1.0.282 | 3 / 8 | |
| 1.0.281 | 2 / 8 | |
| 1.0.280 | 2 / 8 | |
| 1.0.279 | 2 / 8 | |
| 1.0.278 | 2 / 8 | |
| 1.0.277 | 2 / 8 | |
| 1.0.276 | 2 / 8 | |
| 1.0.275 | 2 / 8 | |
| 1.0.274 | 2 / 8 | |
| 1.0.271 | 4 / 8 | |
| 1.0.270 | 6 / 8 | |
| 1.0.269 | 6 / 8 | |
| 1.0.268 | 6 / 8 | |
| 1.0.267 | 6 / 8 | |
| 1.0.266 | 6 / 8 | |
| 1.0.265 | 6 / 8 | |
| 1.0.264 | 6 / 8 | |
| 1.0.263 | 6 / 8 | |
| 1.0.262 | 6 / 8 | |
| 1.0.261 | 6 / 8 | |
| 1.0.260 | 6 / 8 | |
| 1.0.259 | 6 / 8 | |
| 1.0.257 | 6 / 8 | |
| 1.0.140 | 6 / 8 | |
| 1.0.139 | 6 / 8 | |
| 1.0.138 | 6 / 8 | |
| 1.0.137 | 6 / 8 | |
| 1.0.136 | 6 / 8 | |
| 1.0.135 | 6 / 8 | |
| 1.0.134 | 6 / 8 | |
| 1.0.133 | 6 / 8 | |
| 1.0.132 | 6 / 8 | |
| 1.0.131 | 6 / 8 | |
| 1.0.130 | 6 / 8 | |
| 1.0.129 | 6 / 8 | |
| 1.0.128 | 6 / 8 | |
| 1.0.127 | 6 / 8 | |
| 1.0.126 | 6 / 8 | |
| 1.0.125 | 6 / 8 | |
| 1.0.124 | 6 / 8 | |
| 1.0.123 | 6 / 8 | |
| 1.0.122 | 6 / 8 | |
| 1.0.121 | 6 / 8 | |
| 1.0.120 | 6 / 8 | |
| 1.0.119 | 6 / 8 | |
| 1.0.118 | 6 / 8 | |
| 1.0.117 | 6 / 8 | |
| 1.0.116 | 6 / 8 | |
| 1.0.115 | 6 / 8 | |
| 1.0.114 | 6 / 8 | |
| 1.0.113 | 6 / 8 | |
| 1.0.112 | 6 / 8 | |
| 1.0.111 | 6 / 8 | |
| 1.0.110 | 6 / 8 | |
| 1.0.109 | 6 / 8 | |
| 1.0.108 | 6 / 8 | |
| 1.0.107 | 6 / 8 | |
| 1.0.106 | 6 / 8 | |
| 1.0.105 | 6 / 8 |
v1.0.323
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.315
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.135
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.134
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.127
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.