@teambit/linter
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Same-org @teambit/* dep; stable pattern across all teambit package versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Same-org @teambit/* dep; stable pattern across all teambit package versions. | ai | |
| dependencies | unvetted-dep:@teambit/toolbox.time.timer | AI (dependencies): Same-org @teambit/* dep; stable pattern across all teambit package versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentional for teambit component packages; not indicative of malice given age and version count. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance consistently; not a risk signal for this org. | ai | |
| phantom-deps | phantom-dep:@teambit/isolator | AI (phantom-deps): Same-org @teambit scope dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 25 of 225)
| Version | Deps | Published |
|---|---|---|
| 1.0.645 | 14 / 4 | |
| 1.0.644 | 14 / 4 | |
| 1.0.643 | 14 / 4 | |
| 1.0.642 | 14 / 4 | |
| 1.0.640 | 14 / 4 | |
| 1.0.639 | 14 / 4 | |
| 1.0.637 | 14 / 4 | |
| 1.0.636 | 14 / 4 | |
| 1.0.635 | 14 / 4 | |
| 1.0.633 | 14 / 4 | |
| 1.0.632 | 14 / 4 | |
| 1.0.630 | 14 / 4 | |
| 1.0.628 | 14 / 4 | |
| 1.0.626 | 14 / 4 | |
| 1.0.625 | 14 / 4 | |
| 1.0.624 | 14 / 4 | |
| 1.0.622 | 14 / 4 | |
| 1.0.621 | 14 / 4 | |
| 1.0.620 | 14 / 4 | |
| 1.0.619 | 14 / 4 | |
| 1.0.614 | 14 / 4 | |
| 1.0.613 | 14 / 4 | |
| 1.0.612 | 14 / 4 | |
| 1.0.611 | 14 / 4 | |
| 1.0.610 | 14 / 4 |
v1.0.645
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.644
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.643
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.642
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.640
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.639
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.637
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.636
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.635
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.633
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.632
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.630
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.628
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.626
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.625
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.624
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.622
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.621
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.620
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.619
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.614
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.613
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.612
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.611
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.610
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.