@teambit/logger
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @teambit dependency, routine internal monorepo linkage. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): teambit org regularly rotates accounts; publisher track record and package history confirm legitimate ownership. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): First-party @teambit sibling package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.loader | AI (dependencies): First-party @teambit sibling package from the same monorepo. | ai | |
| dependencies | unvetted-dep:dreidels | AI (dependencies): Stable dependency of the teambit ecosystem; no malicious indicators. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Bit component packages commonly omit npm description; not a malware indicator here. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating widespread provenance adoption; no risk signal. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.logger | AI (dependencies): First-party @teambit sibling package from the same monorepo. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): First-party @teambit sibling package from the same monorepo. | ai |
Versions (showing 51 of 212)
| Version | Deps | Published |
|---|---|---|
| 0.0.1442 | 7 / 4 | |
| 0.0.1420 | 7 / 4 | |
| 0.0.1419 | 7 / 4 | |
| 0.0.1418 | 7 / 4 | |
| 0.0.1417 | 7 / 4 | |
| 0.0.1416 | 7 / 4 | |
| 0.0.1415 | 7 / 4 | |
| 0.0.1414 | 7 / 4 | |
| 0.0.1413 | 7 / 4 | |
| 0.0.1409 | 7 / 4 | |
| 0.0.1400 | 7 / 4 | |
| 0.0.1399 | 7 / 4 | |
| 0.0.1398 | 7 / 4 | |
| 0.0.1397 | 7 / 4 | |
| 0.0.1396 | 7 / 4 | |
| 0.0.1394 | 7 / 4 | |
| 0.0.1393 | 7 / 4 | |
| 0.0.1392 | 7 / 4 | |
| 0.0.1391 | 7 / 4 | |
| 0.0.1389 | 7 / 4 | |
| 0.0.1388 | 7 / 4 | |
| 0.0.1386 | 7 / 4 | |
| 0.0.1385 | 7 / 4 | |
| 0.0.1383 | 7 / 4 | |
| 0.0.1377 | 7 / 4 | |
| 0.0.1350 | 7 / 4 | |
| 0.0.1296 | 7 / 4 | |
| 0.0.1295 | 7 / 4 | |
| 0.0.1282 | 7 / 4 | |
| 0.0.1281 | 7 / 4 | |
| 0.0.1280 | 7 / 4 | |
| 0.0.1187 | 7 / 4 | |
| 0.0.1186 | 7 / 4 | |
| 0.0.1142 | 6 / 3 | |
| 0.0.1140 | 5 / 3 | |
| 0.0.1139 | 5 / 3 | |
| 0.0.1138 | 5 / 3 | |
| 0.0.1137 | 5 / 3 | |
| 0.0.1136 | 5 / 3 | |
| 0.0.1135 | 5 / 3 | |
| 0.0.1134 | 5 / 3 | |
| 0.0.1133 | 5 / 3 | |
| 0.0.1132 | 5 / 3 | |
| 0.0.1131 | 5 / 3 | |
| 0.0.1130 | 5 / 3 | |
| 0.0.1129 | 5 / 3 | |
| 0.0.1128 | 5 / 3 | |
| 0.0.1127 | 5 / 3 | |
| 0.0.1126 | 5 / 3 | |
| 0.0.1125 | 5 / 3 | |
| 0.0.1124 | 5 / 3 |
v0.0.1442
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1187
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1186
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1142
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1140
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1139
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1138
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1137
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1136
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1135
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1134
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1132
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1127
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1125
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.