@teambit/prettier
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Known maintainer publish per provenance note; consistent with monorepo maintainer churn. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @teambit dep, consistent with monorepo lockstep versioning. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI publishing across many packages simultaneously; rapid publish is a stable pattern for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with componentId metadata; description not required for internal tooling. | ai | |
| provenance | no-provenance | AI (provenance): Established package; provenance is a best-practice recommendation, not a blocker. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| dependencies | unvetted-dep:@teambit/component.sources | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| dependencies | unvetted-dep:@teambit/workspace-config-files | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| phantom-deps | phantom-dep:@teambit/envs | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for Bit component packages with indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@teambit/component.sources | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for Bit component packages with indirect usage patterns. | ai | |
| dependencies | unvetted-dep:@teambit/defender.prettier.config-mutator | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| dependencies | unvetted-dep:@teambit/envs | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai | |
| dependencies | unvetted-dep:@teambit/formatter | AI (dependencies): Same-org sibling dep from teambit monorepo; expected pattern for Bit platform packages. | ai |
Versions (showing 51 of 135)
| Version | Deps | Published |
|---|---|---|
| 1.0.1064 | 11 / 3 | |
| 1.0.1060 | 11 / 3 | |
| 1.0.1021 | 11 / 3 | |
| 1.0.989 | 11 / 3 | |
| 1.0.972 | 11 / 3 | |
| 1.0.971 | 11 / 3 | |
| 1.0.970 | 11 / 3 | |
| 1.0.968 | 11 / 3 | |
| 1.0.967 | 11 / 3 | |
| 1.0.894 | 11 / 3 | |
| 1.0.584 | 11 / 3 | |
| 1.0.578 | 11 / 3 | |
| 1.0.569 | 11 / 3 | |
| 1.0.562 | 11 / 3 | |
| 1.0.498 | 11 / 3 | |
| 1.0.490 | 11 / 3 | |
| 1.0.480 | 10 / 3 | |
| 1.0.478 | 10 / 3 | |
| 1.0.472 | 10 / 3 | |
| 1.0.471 | 10 / 3 | |
| 1.0.469 | 10 / 3 | |
| 1.0.463 | 10 / 3 | |
| 1.0.457 | 10 / 3 | |
| 1.0.452 | 10 / 3 | |
| 1.0.449 | 10 / 3 | |
| 1.0.446 | 10 / 3 | |
| 1.0.444 | 10 / 3 | |
| 1.0.440 | 10 / 3 | |
| 1.0.438 | 10 / 3 | |
| 1.0.434 | 10 / 3 | |
| 1.0.432 | 10 / 3 | |
| 1.0.431 | 10 / 3 | |
| 1.0.429 | 10 / 3 | |
| 1.0.426 | 10 / 3 | |
| 1.0.425 | 10 / 3 | |
| 1.0.424 | 10 / 3 | |
| 1.0.423 | 10 / 3 | |
| 1.0.421 | 10 / 3 | |
| 1.0.419 | 10 / 3 | |
| 1.0.416 | 10 / 3 | |
| 1.0.415 | 10 / 3 | |
| 1.0.406 | 10 / 4 | |
| 1.0.402 | 10 / 4 | |
| 1.0.400 | 10 / 4 | |
| 1.0.398 | 10 / 4 | |
| 1.0.393 | 10 / 4 | |
| 1.0.392 | 10 / 4 | |
| 1.0.388 | 10 / 4 | |
| 1.0.387 | 10 / 4 | |
| 1.0.382 | 10 / 4 | |
| 1.0.381 | 10 / 4 |
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.894
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (teambit-owner) than the most recent previously approved version (davidfirst) on 2026-02-27, but teambit-owner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.584
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.578
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.569
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.562
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.498
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.490
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.480
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.478
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.472
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.471
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.469
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.463
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.457
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.452
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.449
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.446
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.444
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.440
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.438
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.434
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.432
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.431
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.429
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.426
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.425
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.424
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.423
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.421
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.419
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.416
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.415
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.406
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.402
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.400
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.398
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.393
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.392
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.388
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.387
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.382
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.381
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.