@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 — 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 |
|---|---|---|---|---|
| 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 24 of 24)
| 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 |
v1.0.755
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.754
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.753
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.752
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.751
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.734
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.731
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.728
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.726
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.725
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.719
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.715
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.712
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.611
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.610
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.