@wix/auto_sdk_bookings_availability-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with Wix CI pipeline consolidation, not a hostile takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal wix dev account to wix-ci-publisher CI account; wix-ci-publisher has 1723 approved packages, clearly legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Wix auto-generated SDK package; templated naming, no description/repo are expected patterns for this publisher's SDK suite. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix auto-generated SDK packages consistently omit descriptions; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher does not attach Sigstore provenance; consistent across all approved versions. | ai |
Versions (showing 51 of 143)
| Version | Deps | Published |
|---|---|---|
| 1.0.192 | 3 / 2 | |
| 1.0.191 | 3 / 2 | |
| 1.0.190 | 3 / 2 | |
| 1.0.189 | 3 / 2 | |
| 1.0.188 | 3 / 2 | |
| 1.0.187 | 2 / 2 | |
| 1.0.186 | 2 / 2 | |
| 1.0.185 | 2 / 2 | |
| 1.0.184 | 2 / 2 | |
| 1.0.183 | 2 / 2 | |
| 1.0.182 | 2 / 2 | |
| 1.0.181 | 2 / 2 | |
| 1.0.180 | 2 / 2 | |
| 1.0.179 | 2 / 2 | |
| 1.0.178 | 2 / 2 | |
| 1.0.177 | 2 / 2 | |
| 1.0.176 | 2 / 2 | |
| 1.0.175 | 2 / 2 | |
| 1.0.174 | 2 / 2 | |
| 1.0.173 | 2 / 2 | |
| 1.0.172 | 2 / 2 | |
| 1.0.171 | 2 / 2 | |
| 1.0.170 | 2 / 2 | |
| 1.0.169 | 2 / 2 | |
| 1.0.168 | 2 / 2 | |
| 1.0.167 | 2 / 2 | |
| 1.0.166 | 2 / 2 | |
| 1.0.165 | 2 / 2 | |
| 1.0.164 | 2 / 2 | |
| 1.0.163 | 2 / 2 | |
| 1.0.162 | 2 / 2 | |
| 1.0.161 | 2 / 2 | |
| 1.0.160 | 2 / 2 | |
| 1.0.159 | 2 / 2 | |
| 1.0.158 | 2 / 2 | |
| 1.0.157 | 2 / 2 | |
| 1.0.156 | 2 / 2 | |
| 1.0.155 | 2 / 2 | |
| 1.0.154 | 2 / 2 | |
| 1.0.153 | 2 / 2 | |
| 1.0.152 | 2 / 2 | |
| 1.0.151 | 2 / 2 | |
| 1.0.150 | 2 / 2 | |
| 1.0.149 | 2 / 2 | |
| 1.0.148 | 2 / 2 | |
| 1.0.147 | 2 / 2 | |
| 1.0.146 | 2 / 2 | |
| 1.0.145 | 2 / 2 | |
| 1.0.144 | 2 / 2 | |
| 1.0.143 | 2 / 2 | |
| 1.0.142 | 2 / 2 |
v1.0.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.172
2 findingsThis version was published by a different npm account than previous versions on 2025-09-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.171
2 findingsThis version was published by a different npm account than previous versions on 2025-09-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.170
2 findingsThis version was published by a different npm account than previous versions on 2025-09-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.169
2 findingsThis version was published by a different npm account than previous versions on 2025-09-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.168
2 findingsThis version was published by a different npm account than previous versions on 2025-09-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.167
2 findingsThis version was published by a different npm account than previous versions on 2025-09-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.166
2 findingsThis version was published by a different npm account than previous versions on 2025-07-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.165
2 findingsThis version was published by a different npm account than previous versions on 2025-07-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.164
2 findingsThis version was published by a different npm account than previous versions on 2025-07-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.163
2 findingsThis version was published by a different npm account than previous versions on 2025-07-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.162
2 findingsThis version was published by a different npm account than previous versions on 2025-07-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.161
2 findingsThis version was published by a different npm account than previous versions on 2025-07-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.160
2 findingsThis version was published by a different npm account than previous versions on 2025-07-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.159
2 findingsThis version was published by a different npm account than previous versions on 2025-07-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.158
2 findingsThis version was published by a different npm account than previous versions on 2025-07-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.157
2 findingsThis version was published by a different npm account than previous versions on 2025-07-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.156
2 findingsThis version was published by a different npm account than previous versions on 2025-07-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.155
2 findingsThis version was published by a different npm account than previous versions on 2025-07-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.154
2 findingsThis version was published by a different npm account than previous versions on 2025-07-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.153
2 findingsThis version was published by a different npm account than previous versions on 2025-07-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.152
2 findingsThis version was published by a different npm account than previous versions on 2025-06-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.151
2 findingsThis version was published by a different npm account than previous versions on 2025-06-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.150
2 findingsThis version was published by a different npm account than previous versions on 2025-06-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.149
2 findingsThis version was published by a different npm account than previous versions on 2025-06-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.148
2 findingsThis version was published by a different npm account than previous versions on 2025-06-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.147
2 findingsThis version was published by a different npm account than previous versions on 2025-06-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.146
2 findingsThis version was published by a different npm account than previous versions on 2025-06-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.145
2 findingsThis version was published by a different npm account than previous versions on 2025-06-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.144
2 findingsThis version was published by a different npm account than previous versions on 2025-06-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.143
2 findingsThis version was published by a different npm account than previous versions on 2025-06-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.142
2 findingsThis version was published by a different npm account than previous versions on 2025-06-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.