@teambit/harmony.content.cli-reference
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/mdx.ui.mdx-scope-context | AI (dependencies): Same-org teambit scoped dependency; consistent with the package's established ecosystem context. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable teambit component package; missing description is a consistent pattern across this org, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes without Sigstore provenance consistently; not a risk indicator for this org. | ai | |
| phantom-deps | phantom-dep:@teambit/mdx.ui.mdx-scope-context | AI (phantom-deps): Same-org Bit component dependency; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit runtime polyfill; stable false positive for this package. | ai |
Versions (showing 51 of 439)
| Version | Deps | Published |
|---|---|---|
| 2.0.1070 | 3 / 7 | |
| 2.0.1069 | 3 / 7 | |
| 2.0.1068 | 3 / 7 | |
| 2.0.1067 | 3 / 7 | |
| 2.0.1066 | 3 / 7 | |
| 2.0.1065 | 3 / 7 | |
| 2.0.1064 | 3 / 7 | |
| 2.0.1063 | 3 / 7 | |
| 2.0.1062 | 3 / 7 | |
| 2.0.1061 | 3 / 7 | |
| 2.0.1060 | 3 / 7 | |
| 2.0.1059 | 3 / 7 | |
| 2.0.1058 | 3 / 7 | |
| 2.0.1057 | 3 / 7 | |
| 2.0.1056 | 3 / 7 | |
| 2.0.1055 | 3 / 7 | |
| 2.0.1054 | 3 / 7 | |
| 2.0.1053 | 3 / 7 | |
| 2.0.1052 | 3 / 7 | |
| 2.0.1051 | 3 / 7 | |
| 2.0.1050 | 3 / 7 | |
| 2.0.1049 | 3 / 7 | |
| 2.0.1048 | 3 / 7 | |
| 2.0.1047 | 3 / 7 | |
| 2.0.1046 | 3 / 7 | |
| 2.0.1045 | 3 / 7 | |
| 2.0.1044 | 3 / 7 | |
| 2.0.1043 | 3 / 7 | |
| 2.0.1042 | 3 / 7 | |
| 2.0.1041 | 3 / 7 | |
| 2.0.1040 | 3 / 7 | |
| 2.0.1039 | 3 / 7 | |
| 2.0.1038 | 3 / 7 | |
| 2.0.1037 | 3 / 7 | |
| 2.0.1036 | 3 / 7 | |
| 2.0.1035 | 3 / 7 | |
| 2.0.1034 | 3 / 7 | |
| 2.0.1033 | 3 / 7 | |
| 2.0.1032 | 3 / 7 | |
| 2.0.1031 | 3 / 7 | |
| 2.0.1030 | 3 / 7 | |
| 2.0.1029 | 3 / 7 | |
| 2.0.1028 | 3 / 7 | |
| 2.0.1027 | 3 / 7 | |
| 2.0.1026 | 3 / 7 | |
| 2.0.1025 | 3 / 7 | |
| 2.0.1024 | 3 / 7 | |
| 2.0.1023 | 3 / 7 | |
| 2.0.1022 | 3 / 7 | |
| 2.0.1021 | 3 / 7 | |
| 2.0.1020 | 3 / 7 |
v2.0.1070
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1069
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1068
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1067
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1066
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1065
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1064
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1063
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1062
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1061
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1059
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1058
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1057
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1056
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1055
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1054
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1053
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1052
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1051
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1050
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1049
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1048
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1047
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1046
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1045
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1044
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1043
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1042
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1041
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1040
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1039
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1038
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1037
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1036
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1035
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1034
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1033
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1032
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1031
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1030
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1029
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1028
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1027
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1026
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1025
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1024
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1023
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1022
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1021
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.