@teambit/compositions.ui.composition-compare
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit polyfill dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@teambit/ui-foundation.ui.constants.z-indexes | AI (phantom-deps): Same-org @teambit scope dependency; phantom-dep heuristic unreliable for Bit component packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established teambit component package; missing description is a consistent pattern across their component library, not a malware signal. | ai |
Versions (showing 51 of 121)
| Version | Deps | Published |
|---|---|---|
| 0.0.265 | 16 / 10 | |
| 0.0.264 | 16 / 10 | |
| 0.0.263 | 16 / 10 | |
| 0.0.262 | 16 / 10 | |
| 0.0.261 | 16 / 10 | |
| 0.0.260 | 16 / 10 | |
| 0.0.259 | 12 / 7 | |
| 0.0.258 | 12 / 7 | |
| 0.0.257 | 12 / 7 | |
| 0.0.255 | 12 / 8 | |
| 0.0.254 | 12 / 8 | |
| 0.0.253 | 12 / 8 | |
| 0.0.252 | 12 / 8 | |
| 0.0.251 | 12 / 8 | |
| 0.0.250 | 12 / 8 | |
| 0.0.249 | 12 / 8 | |
| 0.0.248 | 12 / 8 | |
| 0.0.247 | 12 / 8 | |
| 0.0.246 | 12 / 8 | |
| 0.0.245 | 11 / 7 | |
| 0.0.242 | 11 / 7 | |
| 0.0.241 | 11 / 7 | |
| 0.0.240 | 11 / 7 | |
| 0.0.239 | 11 / 7 | |
| 0.0.238 | 11 / 7 | |
| 0.0.237 | 11 / 7 | |
| 0.0.236 | 11 / 7 | |
| 0.0.235 | 12 / 8 | |
| 0.0.234 | 12 / 8 | |
| 0.0.233 | 12 / 8 | |
| 0.0.232 | 12 / 8 | |
| 0.0.231 | 12 / 8 | |
| 0.0.230 | 12 / 8 | |
| 0.0.229 | 12 / 8 | |
| 0.0.228 | 12 / 8 | |
| 0.0.227 | 11 / 7 | |
| 0.0.226 | 11 / 7 | |
| 0.0.225 | 11 / 7 | |
| 0.0.224 | 11 / 7 | |
| 0.0.223 | 11 / 7 | |
| 0.0.222 | 11 / 7 | |
| 0.0.221 | 11 / 7 | |
| 0.0.220 | 11 / 7 | |
| 0.0.219 | 11 / 7 | |
| 0.0.218 | 11 / 7 | |
| 0.0.217 | 11 / 7 | |
| 0.0.216 | 11 / 7 | |
| 0.0.215 | 11 / 7 | |
| 0.0.214 | 11 / 7 | |
| 0.0.213 | 11 / 7 | |
| 0.0.212 | 11 / 7 |
v0.0.259
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.258
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.257
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.255
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.254
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.253
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.252
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.251
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.250
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.249
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.246
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.245
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.242
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.241
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.240
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.239
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.238
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.237
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.236
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.235
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.234
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.233
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.232
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.231
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.230
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.229
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.228
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.227
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.226
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.225
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.224
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.223
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.222
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.221
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.220
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.219
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.218
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.217
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.