@teambit/react.babel.bit-react-transformer
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Stable teambit scoped package; missing description is a consistent pattern across their components, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance consistently; not a risk indicator for this publisher. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.0.47 | 5 / 8 | |
| 1.0.46 | 5 / 8 | |
| 1.0.45 | 5 / 8 | |
| 1.0.44 | 5 / 8 | |
| 1.0.43 | 5 / 8 | |
| 1.0.42 | 5 / 8 | |
| 1.0.41 | 5 / 8 | |
| 1.0.40 | 5 / 8 | |
| 1.0.39 | 5 / 8 | |
| 1.0.38 | 5 / 8 | |
| 1.0.37 | 5 / 8 | |
| 1.0.36 | 5 / 8 | |
| 1.0.35 | 5 / 8 | |
| 1.0.34 | 5 / 8 | |
| 1.0.33 | 5 / 8 | |
| 1.0.31 | 5 / 8 | |
| 1.0.30 | 5 / 8 | |
| 1.0.29 | 5 / 8 | |
| 1.0.28 | 5 / 8 | |
| 1.0.27 | 7 / 6 | |
| 1.0.26 | 7 / 7 | |
| 1.0.25 | 7 / 7 | |
| 1.0.24 | 7 / 7 | |
| 1.0.23 | 7 / 7 | |
| 1.0.22 | 7 / 7 |
v1.0.33
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 2025-04-16, 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.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
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.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.