@teambit/community
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 dep is an official in-monorepo @teambit package, not an external supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is not yet standard practice; stable for this established package. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit ecosystem dependency; expected pattern across all teambit package versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Internal @teambit ecosystem dependency; expected pattern across all teambit package versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Teambit component packages consistently omit descriptions; stable false positive for this namespace. | ai |
Versions (showing 51 of 250)
| Version | Deps | Published |
|---|---|---|
| 1.0.755 | 3 / 2 | |
| 1.0.754 | 3 / 2 | |
| 1.0.753 | 3 / 2 | |
| 1.0.752 | 3 / 2 | |
| 1.0.751 | 3 / 2 | |
| 1.0.748 | 3 / 2 | |
| 1.0.747 | 3 / 2 | |
| 1.0.743 | 3 / 2 | |
| 1.0.742 | 3 / 2 | |
| 1.0.741 | 3 / 2 | |
| 1.0.739 | 3 / 2 | |
| 1.0.738 | 3 / 2 | |
| 1.0.737 | 3 / 2 | |
| 1.0.735 | 3 / 2 | |
| 1.0.734 | 3 / 2 | |
| 1.0.731 | 3 / 2 | |
| 1.0.728 | 3 / 2 | |
| 1.0.726 | 3 / 2 | |
| 1.0.725 | 3 / 2 | |
| 1.0.719 | 3 / 2 | |
| 1.0.715 | 3 / 2 | |
| 1.0.712 | 3 / 2 | |
| 1.0.611 | 4 / 2 | |
| 1.0.610 | 4 / 2 | |
| 1.0.513 | 4 / 2 | |
| 1.0.488 | 4 / 2 | |
| 1.0.487 | 3 / 2 | |
| 1.0.486 | 3 / 2 | |
| 1.0.485 | 3 / 2 | |
| 1.0.484 | 3 / 2 | |
| 1.0.483 | 3 / 2 | |
| 1.0.482 | 3 / 2 | |
| 1.0.481 | 3 / 2 | |
| 1.0.480 | 3 / 2 | |
| 1.0.479 | 3 / 2 | |
| 1.0.478 | 3 / 2 | |
| 1.0.477 | 3 / 2 | |
| 1.0.476 | 3 / 2 | |
| 1.0.475 | 3 / 2 | |
| 1.0.474 | 3 / 2 | |
| 1.0.473 | 3 / 2 | |
| 1.0.472 | 3 / 2 | |
| 1.0.471 | 3 / 2 | |
| 1.0.470 | 3 / 2 | |
| 1.0.469 | 3 / 2 | |
| 1.0.468 | 3 / 2 | |
| 1.0.467 | 3 / 2 | |
| 1.0.466 | 3 / 2 | |
| 1.0.465 | 3 / 2 | |
| 1.0.464 | 3 / 2 | |
| 1.0.463 | 3 / 2 |
v1.0.513
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.488
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-12-10, 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.487
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.486
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.485
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.484
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.483
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.482
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.481
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.479
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.477
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.476
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.475
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.474
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.473
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.470
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.468
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.467
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.466
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.465
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.464
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.