@teambit/git
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/gitconfig | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established @teambit component package; missing description is a known pattern across their releases. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes 1900+ versions without provenance; consistent pattern, not a new risk signal. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @teambit/git is a legitimate Git-integration aspect in the teambit/bit monorepo; not a typosquat of 'got'. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): @teambit/git is a legitimate scoped package; 2-edit distance from 'vite' is coincidental. | ai |
Versions (showing 51 of 547)
| Version | Deps | Published |
|---|---|---|
| 1.0.1077 | 7 / 3 | |
| 1.0.1076 | 7 / 3 | |
| 1.0.1075 | 7 / 3 | |
| 1.0.1074 | 7 / 3 | |
| 1.0.1073 | 7 / 3 | |
| 1.0.1072 | 7 / 3 | |
| 1.0.1071 | 7 / 3 | |
| 1.0.1070 | 7 / 3 | |
| 1.0.1069 | 7 / 3 | |
| 1.0.1068 | 7 / 3 | |
| 1.0.1067 | 7 / 3 | |
| 1.0.1066 | 7 / 3 | |
| 1.0.1065 | 7 / 3 | |
| 1.0.1064 | 7 / 3 | |
| 1.0.1063 | 7 / 3 | |
| 1.0.1062 | 7 / 3 | |
| 1.0.1061 | 7 / 3 | |
| 1.0.1060 | 7 / 3 | |
| 1.0.1059 | 7 / 3 | |
| 1.0.1058 | 7 / 3 | |
| 1.0.1057 | 7 / 3 | |
| 1.0.1056 | 7 / 3 | |
| 1.0.1055 | 7 / 3 | |
| 1.0.1054 | 7 / 3 | |
| 1.0.1053 | 7 / 3 | |
| 1.0.1052 | 7 / 3 | |
| 1.0.1051 | 7 / 3 | |
| 1.0.1050 | 7 / 3 | |
| 1.0.1049 | 7 / 3 | |
| 1.0.1048 | 7 / 3 | |
| 1.0.1047 | 7 / 3 | |
| 1.0.1046 | 7 / 3 | |
| 1.0.1045 | 7 / 3 | |
| 1.0.1044 | 7 / 3 | |
| 1.0.1043 | 7 / 3 | |
| 1.0.1042 | 7 / 3 | |
| 1.0.1041 | 7 / 3 | |
| 1.0.1040 | 7 / 3 | |
| 1.0.1039 | 7 / 3 | |
| 1.0.1038 | 7 / 3 | |
| 1.0.1037 | 7 / 3 | |
| 1.0.1036 | 7 / 3 | |
| 1.0.1035 | 7 / 3 | |
| 1.0.1034 | 7 / 3 | |
| 1.0.1033 | 7 / 3 | |
| 1.0.1032 | 7 / 3 | |
| 1.0.1031 | 7 / 3 | |
| 1.0.1030 | 7 / 3 | |
| 1.0.1029 | 7 / 3 | |
| 1.0.1028 | 7 / 3 | |
| 1.0.1027 | 7 / 3 |
v1.0.1077
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1076
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1075
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1074
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1073
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1072
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1071
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1070
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1069
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1068
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1067
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1066
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1065
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1064
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1063
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1062
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1061
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1059
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1058
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1057
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1056
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1055
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1054
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1053
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1052
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1051
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1050
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1049
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1048
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1047
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1046
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1045
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1044
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1043
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1042
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1041
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1040
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.