@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 35 of 135)
| Version | Deps | Published |
|---|---|---|
| 1.0.291 | 9 / 4 | |
| 1.0.290 | 9 / 4 | |
| 1.0.289 | 9 / 4 | |
| 1.0.288 | 9 / 4 | |
| 1.0.287 | 9 / 4 | |
| 1.0.286 | 9 / 4 | |
| 1.0.285 | 9 / 4 | |
| 1.0.284 | 9 / 4 | |
| 1.0.283 | 9 / 4 | |
| 1.0.282 | 9 / 4 | |
| 1.0.281 | 9 / 4 | |
| 1.0.280 | 9 / 4 | |
| 1.0.279 | 9 / 4 | |
| 1.0.278 | 9 / 4 | |
| 1.0.277 | 9 / 4 | |
| 1.0.276 | 9 / 4 | |
| 1.0.275 | 9 / 4 | |
| 1.0.274 | 9 / 4 | |
| 1.0.273 | 9 / 4 | |
| 1.0.272 | 9 / 4 | |
| 1.0.271 | 9 / 4 | |
| 1.0.270 | 9 / 4 | |
| 1.0.269 | 9 / 4 | |
| 1.0.268 | 9 / 4 | |
| 1.0.267 | 9 / 4 | |
| 1.0.266 | 9 / 4 | |
| 1.0.265 | 9 / 4 | |
| 1.0.264 | 9 / 4 | |
| 1.0.263 | 9 / 4 | |
| 1.0.262 | 9 / 4 | |
| 1.0.261 | 9 / 4 | |
| 1.0.260 | 9 / 4 | |
| 1.0.259 | 9 / 4 | |
| 1.0.258 | 9 / 4 | |
| 1.0.257 | 9 / 4 |
v1.0.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.260
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.259
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 (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-01, but davidfirst 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.258
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 (shohamgilad) than the most recent previously approved version (davidfirst) on 2024-04-30, but shohamgilad 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.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.