@teambit/ipc-events
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): First-party teambit dependency; stable across all versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit monorepo components consistently omit descriptions; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance; consistent across all their packages. | ai |
Versions (showing 100 of 800)
| Version | Deps | Published |
|---|---|---|
| 1.0.674 | 6 / 3 | |
| 1.0.673 | 6 / 3 | |
| 1.0.672 | 6 / 3 | |
| 1.0.671 | 6 / 3 | |
| 1.0.670 | 6 / 3 | |
| 1.0.669 | 6 / 3 | |
| 1.0.668 | 6 / 3 | |
| 1.0.667 | 6 / 3 | |
| 1.0.666 | 6 / 3 | |
| 1.0.665 | 6 / 3 | |
| 1.0.664 | 6 / 3 | |
| 1.0.663 | 6 / 3 | |
| 1.0.662 | 6 / 3 | |
| 1.0.661 | 6 / 3 | |
| 1.0.660 | 6 / 3 | |
| 1.0.659 | 6 / 3 | |
| 1.0.658 | 6 / 3 | |
| 1.0.657 | 6 / 3 | |
| 1.0.656 | 6 / 3 | |
| 1.0.655 | 6 / 3 | |
| 1.0.654 | 6 / 3 | |
| 1.0.653 | 6 / 3 | |
| 1.0.652 | 6 / 3 | |
| 1.0.651 | 6 / 3 | |
| 1.0.650 | 6 / 3 | |
| 1.0.649 | 6 / 3 | |
| 1.0.648 | 6 / 3 | |
| 1.0.647 | 6 / 3 | |
| 1.0.646 | 6 / 3 | |
| 1.0.645 | 6 / 3 | |
| 1.0.644 | 6 / 3 | |
| 1.0.643 | 6 / 3 | |
| 1.0.642 | 6 / 3 | |
| 1.0.641 | 6 / 3 | |
| 1.0.640 | 6 / 3 | |
| 1.0.639 | 6 / 3 | |
| 1.0.638 | 6 / 3 | |
| 1.0.637 | 6 / 3 | |
| 1.0.636 | 6 / 3 | |
| 1.0.635 | 6 / 3 | |
| 1.0.634 | 6 / 3 | |
| 1.0.633 | 6 / 3 | |
| 1.0.632 | 6 / 3 | |
| 1.0.631 | 6 / 3 | |
| 1.0.630 | 6 / 3 | |
| 1.0.629 | 6 / 3 | |
| 1.0.628 | 6 / 3 | |
| 1.0.627 | 6 / 3 | |
| 1.0.626 | 6 / 3 | |
| 1.0.625 | 6 / 3 | |
| 1.0.624 | 6 / 3 | |
| 1.0.623 | 6 / 3 | |
| 1.0.622 | 6 / 3 | |
| 1.0.621 | 6 / 3 | |
| 1.0.620 | 6 / 3 | |
| 1.0.619 | 6 / 3 | |
| 1.0.618 | 6 / 3 | |
| 1.0.617 | 6 / 3 | |
| 1.0.616 | 6 / 3 | |
| 1.0.615 | 6 / 3 | |
| 1.0.614 | 6 / 3 | |
| 1.0.613 | 6 / 3 | |
| 1.0.612 | 6 / 3 | |
| 1.0.611 | 6 / 3 | |
| 1.0.610 | 6 / 3 | |
| 1.0.608 | 6 / 3 | |
| 1.0.606 | 6 / 3 | |
| 1.0.604 | 6 / 3 | |
| 1.0.602 | 6 / 3 | |
| 1.0.600 | 6 / 3 | |
| 1.0.598 | 6 / 3 | |
| 1.0.596 | 6 / 3 | |
| 1.0.594 | 6 / 3 | |
| 1.0.592 | 6 / 3 | |
| 1.0.590 | 6 / 3 | |
| 1.0.588 | 6 / 3 | |
| 1.0.587 | 6 / 3 | |
| 1.0.586 | 6 / 3 | |
| 1.0.585 | 6 / 3 | |
| 1.0.584 | 6 / 3 | |
| 1.0.583 | 6 / 3 | |
| 1.0.582 | 6 / 3 | |
| 1.0.581 | 6 / 3 | |
| 1.0.580 | 6 / 3 | |
| 1.0.579 | 6 / 3 | |
| 1.0.578 | 6 / 3 | |
| 1.0.577 | 6 / 3 | |
| 1.0.576 | 6 / 3 | |
| 1.0.575 | 6 / 3 | |
| 1.0.574 | 6 / 3 | |
| 1.0.573 | 6 / 3 | |
| 1.0.572 | 6 / 3 | |
| 1.0.571 | 6 / 3 | |
| 1.0.570 | 6 / 3 | |
| 1.0.569 | 6 / 3 | |
| 1.0.568 | 6 / 3 | |
| 1.0.567 | 6 / 3 | |
| 1.0.566 | 6 / 3 | |
| 1.0.565 | 6 / 3 | |
| 1.0.564 | 6 / 3 |
v1.0.608
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.606
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.604
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.602
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.600
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.598
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.596
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.594
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.592
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.590
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.588
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.587
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.586
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.585
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.584
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.583
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.582
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.581
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.580
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.579
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.578
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.577
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.576
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.575
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.574
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.573
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.572
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.571
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.570
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.569
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.568
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.567
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.566
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.565
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.564
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.