@teambit/component-sizer
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo lockstep releases publish many packages in quick succession routinely. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component with valid repo and keywords; description gap is stable. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance absence is consistent across versions. | ai | |
| dependencies | unvetted-dep:@teambit/graphql | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/preview | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/component | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/ui | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/design.ui.pill-label | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/component.ui.component-size | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/base-react.themes.theme-switcher | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/ui-foundation.ui.react-router.use-query | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/design.ui.tooltip | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/docs | AI (dependencies): Sibling @teambit/* dep in the established Bit monorepo ecosystem; not a malware signal. | ai |
Versions (showing 100 of 496)
| Version | Deps | Published |
|---|---|---|
| 1.0.559 | 13 / 2 | |
| 1.0.558 | 13 / 2 | |
| 1.0.557 | 13 / 2 | |
| 1.0.556 | 13 / 2 | |
| 1.0.555 | 13 / 2 | |
| 1.0.554 | 13 / 2 | |
| 1.0.553 | 13 / 2 | |
| 1.0.552 | 13 / 2 | |
| 1.0.551 | 13 / 2 | |
| 1.0.550 | 13 / 2 | |
| 1.0.549 | 13 / 2 | |
| 1.0.548 | 13 / 2 | |
| 1.0.547 | 13 / 2 | |
| 1.0.546 | 13 / 2 | |
| 1.0.545 | 13 / 2 | |
| 1.0.544 | 13 / 2 | |
| 1.0.543 | 13 / 2 | |
| 1.0.542 | 13 / 2 | |
| 1.0.541 | 13 / 2 | |
| 1.0.540 | 13 / 2 | |
| 1.0.539 | 13 / 2 | |
| 1.0.538 | 13 / 2 | |
| 1.0.537 | 13 / 2 | |
| 1.0.536 | 13 / 2 | |
| 1.0.535 | 13 / 2 | |
| 1.0.534 | 13 / 2 | |
| 1.0.533 | 13 / 2 | |
| 1.0.532 | 13 / 2 | |
| 1.0.531 | 13 / 2 | |
| 1.0.530 | 13 / 2 | |
| 1.0.529 | 13 / 2 | |
| 1.0.528 | 13 / 2 | |
| 1.0.527 | 13 / 2 | |
| 1.0.526 | 13 / 2 | |
| 1.0.525 | 13 / 2 | |
| 1.0.524 | 13 / 2 | |
| 1.0.523 | 13 / 2 | |
| 1.0.522 | 13 / 2 | |
| 1.0.521 | 13 / 2 | |
| 1.0.520 | 13 / 2 | |
| 1.0.519 | 13 / 2 | |
| 1.0.518 | 13 / 2 | |
| 1.0.517 | 13 / 2 | |
| 1.0.516 | 13 / 2 | |
| 1.0.515 | 13 / 2 | |
| 1.0.514 | 13 / 2 | |
| 1.0.513 | 13 / 2 | |
| 1.0.512 | 13 / 2 | |
| 1.0.511 | 13 / 2 | |
| 1.0.510 | 13 / 2 | |
| 1.0.509 | 13 / 2 | |
| 1.0.508 | 13 / 2 | |
| 1.0.507 | 13 / 2 | |
| 1.0.506 | 13 / 2 | |
| 1.0.505 | 13 / 2 | |
| 1.0.504 | 13 / 2 | |
| 1.0.503 | 13 / 2 | |
| 1.0.502 | 13 / 2 | |
| 1.0.501 | 13 / 2 | |
| 1.0.500 | 13 / 2 | |
| 1.0.499 | 13 / 2 | |
| 1.0.498 | 13 / 2 | |
| 1.0.497 | 13 / 2 | |
| 1.0.496 | 13 / 2 | |
| 1.0.495 | 13 / 2 | |
| 1.0.494 | 13 / 2 | |
| 1.0.493 | 13 / 2 | |
| 1.0.492 | 13 / 2 | |
| 1.0.491 | 13 / 2 | |
| 1.0.490 | 13 / 2 | |
| 1.0.489 | 13 / 2 | |
| 1.0.488 | 13 / 2 | |
| 1.0.487 | 13 / 2 | |
| 1.0.486 | 13 / 2 | |
| 1.0.485 | 13 / 2 | |
| 1.0.484 | 13 / 2 | |
| 1.0.483 | 13 / 2 | |
| 1.0.482 | 13 / 2 | |
| 1.0.481 | 13 / 2 | |
| 1.0.480 | 13 / 2 | |
| 1.0.479 | 13 / 2 | |
| 1.0.478 | 13 / 2 | |
| 1.0.477 | 13 / 2 | |
| 1.0.476 | 13 / 2 | |
| 1.0.475 | 13 / 2 | |
| 1.0.474 | 13 / 2 | |
| 1.0.473 | 13 / 2 | |
| 1.0.472 | 13 / 2 | |
| 1.0.471 | 13 / 2 | |
| 1.0.470 | 13 / 2 | |
| 1.0.469 | 13 / 2 | |
| 1.0.468 | 13 / 2 | |
| 1.0.467 | 13 / 2 | |
| 1.0.466 | 13 / 2 | |
| 1.0.465 | 13 / 2 | |
| 1.0.464 | 13 / 2 | |
| 1.0.463 | 13 / 2 | |
| 1.0.462 | 13 / 2 | |
| 1.0.461 | 13 / 2 | |
| 1.0.460 | 13 / 2 |
v1.0.559
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.558
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.557
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.556
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.555
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.554
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.553
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.552
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.551
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.550
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.549
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.548
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.547
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.546
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.545
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.544
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.543
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.542
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.541
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.540
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.539
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.538
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.537
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.536
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.535
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.534
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.533
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.532
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.531
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.530
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.529
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.528
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.527
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.526
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.525
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.524
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.523
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.522
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.521
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.520
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.519
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.518
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.517
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.516
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.515
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.514
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.513
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.512
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.511
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.510
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.509
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.508
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.507
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.506
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.505
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.504
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.503
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.502
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.501
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.500
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.499
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.498
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.497
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.496
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.495
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.494
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.493
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.492
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.491
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.490
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.489
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.488
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.487
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.486
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.485
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.484
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.483
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.482
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.481
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.480
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.479
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.478
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.477
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.476
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.475
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.474
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.473
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.472
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.471
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.470
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.469
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.468
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.467
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.466
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.465
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.464
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.463
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.462
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.461
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.460
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.