@teambit/vue-aspect
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Bit ecosystem package; missing description is common in monorepo-published components. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publisher; provenance not yet enabled but not a blocker for established ecosystem. | ai | |
| dependencies | unvetted-dep:@teambit/schema | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/api-reference | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/documenter.ui.table | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/ui | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/semantics.entities.semantic-schema | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/api-reference.models.api-node-renderer | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/api-reference.models.api-reference-model | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/documenter.ui.table-row | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Internal @teambit ecosystem dep; consistent with Bit platform package family. | ai |
Versions (showing 100 of 339)
| Version | Deps | Published |
|---|---|---|
| 0.0.385 | 12 / 1 | |
| 0.0.384 | 12 / 1 | |
| 0.0.383 | 12 / 1 | |
| 0.0.382 | 12 / 1 | |
| 0.0.381 | 12 / 1 | |
| 0.0.380 | 12 / 1 | |
| 0.0.379 | 12 / 1 | |
| 0.0.378 | 12 / 1 | |
| 0.0.377 | 12 / 1 | |
| 0.0.376 | 12 / 1 | |
| 0.0.375 | 12 / 1 | |
| 0.0.374 | 12 / 1 | |
| 0.0.373 | 12 / 1 | |
| 0.0.372 | 12 / 1 | |
| 0.0.371 | 12 / 1 | |
| 0.0.370 | 12 / 1 | |
| 0.0.369 | 12 / 1 | |
| 0.0.368 | 12 / 1 | |
| 0.0.367 | 12 / 1 | |
| 0.0.366 | 12 / 1 | |
| 0.0.365 | 12 / 1 | |
| 0.0.364 | 12 / 1 | |
| 0.0.363 | 12 / 1 | |
| 0.0.362 | 12 / 1 | |
| 0.0.361 | 12 / 1 | |
| 0.0.360 | 12 / 1 | |
| 0.0.359 | 12 / 1 | |
| 0.0.358 | 12 / 1 | |
| 0.0.357 | 12 / 1 | |
| 0.0.356 | 12 / 1 | |
| 0.0.355 | 12 / 1 | |
| 0.0.354 | 12 / 1 | |
| 0.0.353 | 12 / 1 | |
| 0.0.352 | 12 / 1 | |
| 0.0.351 | 12 / 1 | |
| 0.0.350 | 12 / 1 | |
| 0.0.349 | 12 / 1 | |
| 0.0.348 | 12 / 1 | |
| 0.0.347 | 12 / 1 | |
| 0.0.346 | 12 / 1 | |
| 0.0.345 | 12 / 1 | |
| 0.0.344 | 12 / 1 | |
| 0.0.343 | 12 / 1 | |
| 0.0.342 | 12 / 1 | |
| 0.0.341 | 12 / 1 | |
| 0.0.340 | 12 / 1 | |
| 0.0.339 | 12 / 1 | |
| 0.0.338 | 12 / 1 | |
| 0.0.337 | 12 / 1 | |
| 0.0.336 | 12 / 1 | |
| 0.0.335 | 12 / 1 | |
| 0.0.334 | 12 / 1 | |
| 0.0.291 | 12 / 1 | |
| 0.0.290 | 12 / 1 | |
| 0.0.289 | 12 / 1 | |
| 0.0.288 | 12 / 1 | |
| 0.0.287 | 12 / 1 | |
| 0.0.286 | 12 / 1 | |
| 0.0.285 | 12 / 1 | |
| 0.0.284 | 12 / 1 | |
| 0.0.283 | 12 / 1 | |
| 0.0.282 | 12 / 1 | |
| 0.0.281 | 12 / 1 | |
| 0.0.280 | 12 / 1 | |
| 0.0.279 | 12 / 1 | |
| 0.0.278 | 12 / 1 | |
| 0.0.277 | 12 / 1 | |
| 0.0.276 | 12 / 1 | |
| 0.0.275 | 12 / 1 | |
| 0.0.273 | 12 / 1 | |
| 0.0.272 | 12 / 1 | |
| 0.0.271 | 12 / 1 | |
| 0.0.270 | 12 / 1 | |
| 0.0.269 | 12 / 1 | |
| 0.0.268 | 12 / 1 | |
| 0.0.267 | 12 / 1 | |
| 0.0.266 | 12 / 1 | |
| 0.0.265 | 12 / 1 | |
| 0.0.264 | 12 / 1 | |
| 0.0.263 | 12 / 1 | |
| 0.0.262 | 12 / 1 | |
| 0.0.261 | 12 / 1 | |
| 0.0.260 | 12 / 1 | |
| 0.0.259 | 12 / 1 | |
| 0.0.258 | 12 / 1 | |
| 0.0.257 | 12 / 1 | |
| 0.0.256 | 12 / 1 | |
| 0.0.255 | 12 / 1 | |
| 0.0.254 | 12 / 1 | |
| 0.0.253 | 12 / 1 | |
| 0.0.252 | 12 / 1 | |
| 0.0.251 | 12 / 1 | |
| 0.0.250 | 12 / 1 | |
| 0.0.249 | 12 / 1 | |
| 0.0.248 | 12 / 1 | |
| 0.0.247 | 12 / 1 | |
| 0.0.246 | 12 / 1 | |
| 0.0.245 | 12 / 1 | |
| 0.0.244 | 12 / 1 | |
| 0.0.243 | 12 / 1 |
v0.0.385
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.384
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.383
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.382
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.381
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.380
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.379
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.378
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.377
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.376
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.375
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.374
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.373
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.372
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.371
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.370
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.369
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.368
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.367
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.366
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.365
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.364
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.363
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.362
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.361
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.360
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.359
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.358
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.357
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.356
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.355
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.354
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.353
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.352
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.351
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.350
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.349
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.348
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.347
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.346
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.345
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.344
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.343
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.342
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.341
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.340
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.339
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.338
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.337
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.336
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.335
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.260
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.259
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.258
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.256
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.255
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.254
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.253
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.252
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.251
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.250
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.249
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.248
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.247
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.246
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.245
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.244
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.243
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.