@teambit/yarn
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:@yarnpkg/cli | AI (dependencies): Core Yarn CLI dependency; expected and stable for this Yarn integration package. | ai | |
| dependencies | unvetted-dep:@yarnpkg/plugin-npm | AI (dependencies): Standard Yarn plugin dependency; expected for this Yarn integration package. | ai | |
| dependencies | unvetted-dep:@teambit/pkg.entities.registry | AI (dependencies): Same-org @teambit scoped dependency; expected for teambit ecosystem packages. | ai | |
| typosquat | typosquat.levenshtein:yargs | AI (typosquat): @teambit/yarn is a Yarn package manager integration in the Bit monorepo; not a typosquat of yargs. | ai | |
| phantom-deps | phantom-dep:@teambit/pkg.entities.registry | AI (phantom-deps): Same-org dependency; phantom-dep heuristic is unreliable for monorepo component packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo component; missing description is a cosmetic issue, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit monorepo does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.989 | 23 / 5 | |
| 1.0.972 | 23 / 5 | |
| 1.0.971 | 23 / 5 | |
| 1.0.970 | 23 / 5 | |
| 1.0.969 | 23 / 5 | |
| 1.0.968 | 23 / 5 | |
| 1.0.955 | 23 / 5 | |
| 1.0.951 | 23 / 5 | |
| 1.0.950 | 23 / 5 | |
| 1.0.945 | 23 / 5 | |
| 1.0.943 | 23 / 5 | |
| 1.0.938 | 23 / 5 | |
| 1.0.925 | 23 / 5 |
v1.0.989
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.972
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.971
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.970
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.969
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.955
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.951
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.950
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.945
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.943
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.938
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.925
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.