@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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Wix CI publisher routinely publishes rapidly via automated pipelines; stable pattern for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Wix org internal maintainer rotation; consistent with large org publishing patterns. | ai | |
| 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 | |
| provenance | no-provenance | AI (provenance): Wix CI publisher consistently publishes without provenance attestation across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix internal SDK package; missing description is consistent across the package family. | ai |
Versions (showing 63 of 163)
| Version | Deps | Published |
|---|---|---|
| 1.0.163 | 5 / 2 | |
| 1.0.162 | 5 / 2 | |
| 1.0.161 | 5 / 2 | |
| 1.0.160 | 5 / 2 | |
| 1.0.159 | 5 / 2 | |
| 1.0.158 | 5 / 2 | |
| 1.0.157 | 5 / 2 | |
| 1.0.156 | 5 / 2 | |
| 1.0.155 | 5 / 2 | |
| 1.0.154 | 5 / 2 | |
| 1.0.153 | 5 / 2 | |
| 1.0.152 | 5 / 2 | |
| 1.0.151 | 5 / 2 | |
| 1.0.150 | 5 / 2 | |
| 1.0.149 | 5 / 2 | |
| 1.0.148 | 5 / 2 | |
| 1.0.147 | 5 / 2 | |
| 1.0.146 | 5 / 2 | |
| 1.0.145 | 5 / 2 | |
| 1.0.144 | 5 / 2 | |
| 1.0.143 | 5 / 2 | |
| 1.0.142 | 5 / 2 | |
| 1.0.141 | 5 / 2 | |
| 1.0.140 | 5 / 2 | |
| 1.0.139 | 5 / 2 | |
| 1.0.138 | 5 / 2 | |
| 1.0.137 | 5 / 2 | |
| 1.0.136 | 5 / 2 | |
| 1.0.135 | 5 / 2 | |
| 1.0.134 | 5 / 2 | |
| 1.0.133 | 5 / 2 | |
| 1.0.132 | 5 / 2 | |
| 1.0.131 | 5 / 2 | |
| 1.0.130 | 5 / 2 | |
| 1.0.129 | 5 / 2 | |
| 1.0.128 | 5 / 1 | |
| 1.0.127 | 5 / 1 | |
| 1.0.126 | 5 / 1 | |
| 1.0.125 | 5 / 1 | |
| 1.0.124 | 5 / 1 | |
| 1.0.123 | 5 / 1 | |
| 1.0.122 | 5 / 1 | |
| 1.0.121 | 5 / 1 | |
| 1.0.120 | 5 / 1 | |
| 1.0.119 | 5 / 1 | |
| 1.0.118 | 5 / 1 | |
| 1.0.117 | 5 / 1 | |
| 1.0.116 | 5 / 1 | |
| 1.0.115 | 5 / 1 | |
| 1.0.114 | 5 / 2 | |
| 1.0.113 | 5 / 2 | |
| 1.0.112 | 5 / 2 | |
| 1.0.111 | 5 / 1 | |
| 1.0.110 | 5 / 1 | |
| 1.0.109 | 5 / 1 | |
| 1.0.108 | 5 / 1 | |
| 1.0.107 | 5 / 1 | |
| 1.0.106 | 5 / 1 | |
| 1.0.105 | 5 / 1 | |
| 1.0.104 | 5 / 1 | |
| 1.0.103 | 5 / 1 | |
| 1.0.102 | 5 / 1 | |
| 1.0.101 | 5 / 1 |
v1.0.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.154
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.153
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.152
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.151
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.150
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.149
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.148
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.147
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.146
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.145
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.144
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.143
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.142
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.141
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.140
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.139
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.138
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.137
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.136
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.134
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.132
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.127
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.0.104
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.103
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.102
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.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.