@wix/calendar
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@wix/auto_sdk_calendar_participations | AI (dependencies): Dependency removed in this version; finding is stale. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_calendar_schedules | AI (dependencies): Sibling Wix auto-SDK package following the same naming convention; not a third-party unvetted dep. | ai | |
| dependencies | unvetted-dep:@wix/auto_sdk_calendar_schedule-time-frames | AI (dependencies): Sibling Wix auto-SDK package following the same naming convention; not a third-party unvetted dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK package; mass-production naming, no description, and no repo URL are expected for this publisher's pipeline. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix internal SDK package; missing description is consistent across the package family. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher consistently publishes without provenance attestation across all versions. | ai |
Versions (showing 51 of 153)
| Version | Deps | Published |
|---|---|---|
| 1.0.258 | 5 / 2 | |
| 1.0.257 | 5 / 2 | |
| 1.0.256 | 5 / 2 | |
| 1.0.255 | 5 / 2 | |
| 1.0.254 | 5 / 2 | |
| 1.0.253 | 5 / 2 | |
| 1.0.252 | 5 / 2 | |
| 1.0.251 | 5 / 2 | |
| 1.0.248 | 5 / 2 | |
| 1.0.245 | 5 / 2 | |
| 1.0.244 | 5 / 2 | |
| 1.0.243 | 5 / 2 | |
| 1.0.242 | 5 / 2 | |
| 1.0.241 | 5 / 2 | |
| 1.0.240 | 5 / 2 | |
| 1.0.239 | 5 / 2 | |
| 1.0.238 | 5 / 2 | |
| 1.0.237 | 5 / 2 | |
| 1.0.236 | 5 / 2 | |
| 1.0.235 | 5 / 2 | |
| 1.0.234 | 5 / 2 | |
| 1.0.233 | 5 / 2 | |
| 1.0.232 | 5 / 2 | |
| 1.0.231 | 5 / 2 | |
| 1.0.230 | 5 / 2 | |
| 1.0.229 | 5 / 2 | |
| 1.0.228 | 5 / 2 | |
| 1.0.227 | 5 / 2 | |
| 1.0.226 | 5 / 2 | |
| 1.0.225 | 5 / 2 | |
| 1.0.224 | 5 / 2 | |
| 1.0.223 | 5 / 2 | |
| 1.0.222 | 5 / 2 | |
| 1.0.221 | 5 / 2 | |
| 1.0.220 | 5 / 2 | |
| 1.0.219 | 5 / 2 | |
| 1.0.218 | 5 / 2 | |
| 1.0.217 | 5 / 2 | |
| 1.0.216 | 5 / 2 | |
| 1.0.215 | 5 / 2 | |
| 1.0.214 | 5 / 2 | |
| 1.0.213 | 5 / 2 | |
| 1.0.212 | 5 / 2 | |
| 1.0.211 | 5 / 2 | |
| 1.0.210 | 5 / 2 | |
| 1.0.209 | 5 / 2 | |
| 1.0.208 | 5 / 2 | |
| 1.0.207 | 5 / 2 | |
| 1.0.206 | 5 / 2 | |
| 1.0.205 | 5 / 2 | |
| 1.0.204 | 5 / 2 |
v1.0.258
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.256
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.255
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.254
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.253
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.252
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.248
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.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.244
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.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.242
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.241
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.240
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.239
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.238
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.237
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.236
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.235
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.234
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.233
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.232
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.231
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.230
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.229
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.228
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.227
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.226
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.225
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.224
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.223
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.222
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.221
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.220
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.219
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.218
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.217
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.216
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.215
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.214
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.213
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.212
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.211
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.210
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.209
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.208
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.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.206
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.205
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.204
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.