@teambit/multi-compiler
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): Stable for this package; 1969-day history and 2784 versions indicate established, non-malicious project. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is advisory; package predates Sigstore adoption and has long track record. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit monorepo dependency; stable ecosystem pattern across all teambit packages. | ai | |
| dependencies | unvetted-dep:@teambit/compiler | AI (dependencies): Internal @teambit monorepo dependency; stable ecosystem pattern across all teambit packages. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Internal @teambit monorepo dependency; stable ecosystem pattern across all teambit packages. | ai | |
| dependencies | unvetted-dep:@teambit/pipelines.modules.merge-component-results | AI (dependencies): Internal @teambit monorepo dependency; stable ecosystem pattern across all teambit packages. | ai | |
| dependencies | unvetted-dep:@teambit/component | AI (dependencies): Internal @teambit monorepo dependency; stable ecosystem pattern across all teambit packages. | ai | |
| dependencies | unvetted-dep:@teambit/builder | AI (dependencies): Internal @teambit monorepo dependency; stable ecosystem pattern across all teambit packages. | ai |
Versions (showing 4 of 407)
| Version | Deps | Published |
|---|---|---|
| 1.0.613 | 7 / 3 | |
| 1.0.612 | 7 / 3 | |
| 1.0.611 | 7 / 3 | |
| 1.0.610 | 7 / 3 |
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.