@teambit/global-config
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/legacy.global-config | AI (dependencies): First-party @teambit monorepo sibling package, part of normal Harmony refactor. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are all official @teambit sibling packages, not external supply-chain risk. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Long-established teambit org package; removal of learn-bit without new additions is consistent with routine org maintenance. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established monorepo package; missing description is stable pattern. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm has provenance; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@teambit/scope.remotes | AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/config-store | AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline artifact, not a risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope | AI (dependencies): Sibling @teambit monorepo package; unvetted status is a pipeline artifact, not a risk signal. | ai |
Versions (showing 51 of 233)
| Version | Deps | Published |
|---|---|---|
| 0.0.1355 | 12 / 5 | |
| 0.0.1353 | 12 / 5 | |
| 0.0.1331 | 12 / 5 | |
| 0.0.1330 | 12 / 5 | |
| 0.0.1329 | 12 / 5 | |
| 0.0.1328 | 12 / 5 | |
| 0.0.1327 | 12 / 5 | |
| 0.0.1326 | 12 / 5 | |
| 0.0.1323 | 12 / 5 | |
| 0.0.1321 | 12 / 5 | |
| 0.0.1320 | 12 / 5 | |
| 0.0.1319 | 12 / 5 | |
| 0.0.1317 | 12 / 5 | |
| 0.0.1316 | 12 / 5 | |
| 0.0.1315 | 12 / 5 | |
| 0.0.1314 | 12 / 5 | |
| 0.0.1313 | 12 / 5 | |
| 0.0.1311 | 12 / 5 | |
| 0.0.1310 | 12 / 5 | |
| 0.0.1288 | 12 / 5 | |
| 0.0.1287 | 12 / 5 | |
| 0.0.1242 | 12 / 5 | |
| 0.0.1240 | 12 / 5 | |
| 0.0.1231 | 12 / 5 | |
| 0.0.1216 | 12 / 5 | |
| 0.0.1215 | 12 / 5 | |
| 0.0.1199 | 12 / 5 | |
| 0.0.1198 | 12 / 5 | |
| 0.0.1197 | 12 / 5 | |
| 0.0.1195 | 12 / 5 | |
| 0.0.1194 | 12 / 5 | |
| 0.0.1193 | 12 / 5 | |
| 0.0.1192 | 12 / 5 | |
| 0.0.1191 | 12 / 5 | |
| 0.0.1190 | 12 / 5 | |
| 0.0.1093 | 12 / 5 | |
| 0.0.1089 | 12 / 5 | |
| 0.0.1068 | 12 / 5 | |
| 0.0.1067 | 8 / 5 | |
| 0.0.1066 | 8 / 5 | |
| 0.0.1065 | 8 / 5 | |
| 0.0.1064 | 8 / 5 | |
| 0.0.1063 | 8 / 5 | |
| 0.0.1062 | 8 / 5 | |
| 0.0.1061 | 8 / 5 | |
| 0.0.1060 | 8 / 5 | |
| 0.0.1059 | 8 / 5 | |
| 0.0.1058 | 8 / 5 | |
| 0.0.1057 | 8 / 5 | |
| 0.0.1056 | 8 / 5 | |
| 0.0.1055 | 8 / 5 |
v0.0.1355
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1353
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1093
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1089
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1068
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.
v0.0.1067
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1066
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1065
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1064
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1063
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1062
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1061
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1059
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1058
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1057
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1056
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1055
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.