@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 12 of 212)
| Version | Deps | Published |
|---|---|---|
| 0.0.967 | 5 / 4 | |
| 0.0.966 | 5 / 4 | |
| 0.0.965 | 5 / 4 | |
| 0.0.964 | 5 / 4 | |
| 0.0.963 | 5 / 4 | |
| 0.0.962 | 5 / 4 | |
| 0.0.961 | 5 / 4 | |
| 0.0.960 | 5 / 4 | |
| 0.0.959 | 5 / 4 | |
| 0.0.958 | 5 / 4 | |
| 0.0.957 | 5 / 4 | |
| 0.0.956 | 5 / 4 |
v0.0.967
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.966
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.965
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.964
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.963
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.962
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.961
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.960
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.959
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.958
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.957
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.956
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.