@teambit/eject
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 | new-deps-added | AI (publish-pattern): New deps are same-org @teambit packages, normal for this monorepo's release cadence. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit publishes hundreds of coordinated monorepo packages in rapid succession; this is expected CI automation behavior. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with long history; missing description is stable metadata issue, not malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is infrastructure choice, not a security defect for this mature package. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher. | ai | |
| dependencies | unvetted-dep:@teambit/scope.remotes | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher. | ai | |
| dependencies | unvetted-dep:@teambit/component.sources | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer-component | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher. | ai | |
| dependencies | unvetted-dep:@teambit/pkg.modules.component-package-name | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): First-party @teambit sibling dep from the same monorepo publisher; stable pattern across all versions. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @teambit/eject is a legitimate Bit workspace component; levenshtein match to 'jest' is a false positive. | ai |
Versions (showing 51 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.0.1064 | 14 / 2 | |
| 1.0.1060 | 14 / 2 | |
| 1.0.1056 | 14 / 2 | |
| 1.0.1055 | 14 / 2 | |
| 1.0.1052 | 14 / 2 | |
| 1.0.1051 | 14 / 2 | |
| 1.0.1021 | 14 / 2 | |
| 1.0.1008 | 14 / 2 | |
| 1.0.996 | 14 / 2 | |
| 1.0.990 | 14 / 2 | |
| 1.0.983 | 14 / 2 | |
| 1.0.976 | 14 / 2 | |
| 1.0.972 | 14 / 2 | |
| 1.0.971 | 14 / 2 | |
| 1.0.970 | 14 / 2 | |
| 1.0.968 | 14 / 2 | |
| 1.0.955 | 14 / 2 | |
| 1.0.333 | 10 / 3 | |
| 1.0.332 | 9 / 3 | |
| 1.0.331 | 9 / 3 | |
| 1.0.330 | 7 / 3 | |
| 1.0.329 | 7 / 3 | |
| 1.0.328 | 7 / 3 | |
| 1.0.327 | 7 / 3 | |
| 1.0.326 | 7 / 3 | |
| 1.0.325 | 7 / 3 | |
| 1.0.324 | 7 / 3 | |
| 1.0.323 | 7 / 3 | |
| 1.0.322 | 7 / 3 | |
| 1.0.321 | 7 / 3 | |
| 1.0.320 | 7 / 3 | |
| 1.0.319 | 7 / 3 | |
| 1.0.318 | 7 / 3 | |
| 1.0.317 | 7 / 3 | |
| 1.0.316 | 7 / 3 | |
| 1.0.315 | 7 / 3 | |
| 1.0.314 | 7 / 3 | |
| 1.0.313 | 7 / 3 | |
| 1.0.312 | 7 / 3 | |
| 1.0.311 | 7 / 3 | |
| 1.0.310 | 7 / 3 | |
| 1.0.309 | 7 / 3 | |
| 1.0.308 | 7 / 3 | |
| 1.0.307 | 7 / 3 | |
| 1.0.306 | 7 / 3 | |
| 1.0.305 | 7 / 3 | |
| 1.0.304 | 7 / 3 | |
| 1.0.303 | 7 / 3 | |
| 1.0.302 | 7 / 3 | |
| 1.0.301 | 7 / 3 | |
| 1.0.300 | 7 / 3 |
v1.0.1064
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1056
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1055
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1052
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1051
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.983
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.976
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.333
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.332
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.331
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.330
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.329
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.328
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.327
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.326
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.325
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.324
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.323
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.315
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.312
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.310
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.309
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.307
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.306
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.305
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.304
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.303
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.302
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.301
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.300
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.