@teambit/cli
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.utils | AI (dependencies): First-party teambit monorepo package, same publisher as approved siblings. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Same-org first-party dependency added to a long-running monorepo package. | ai | |
| dependencies | unvetted-dep:@teambit/workspace.modules.workspace-locator | AI (dependencies): First-party @teambit scoped package; consistent with the rest of the dependency tree for this well-established package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established scoped package with clear purpose; missing description is stable pattern. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm packages have provenance; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.logger | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.analytics | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @teambit/cli package; Levenshtein match to 'joi' is a false positive with no brand impersonation. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/bit.get-bit-version | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.cli.error | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.loader | AI (dependencies): Sibling @teambit/* package from the same publisher/ecosystem; stable false positive. | ai |
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.0.1351 | 18 / 6 | |
| 0.0.1349 | 17 / 6 | |
| 0.0.1327 | 17 / 6 | |
| 0.0.1326 | 17 / 6 | |
| 0.0.1325 | 17 / 6 | |
| 0.0.1324 | 17 / 6 | |
| 0.0.1323 | 17 / 6 | |
| 0.0.1322 | 17 / 6 | |
| 0.0.1321 | 17 / 6 | |
| 0.0.1320 | 17 / 6 | |
| 0.0.1316 | 17 / 6 | |
| 0.0.1315 | 17 / 6 | |
| 0.0.1314 | 17 / 6 | |
| 0.0.1313 | 17 / 6 | |
| 0.0.1312 | 17 / 6 | |
| 0.0.1311 | 17 / 6 | |
| 0.0.1310 | 16 / 5 | |
| 0.0.1309 | 16 / 5 | |
| 0.0.1308 | 16 / 5 | |
| 0.0.1307 | 16 / 5 | |
| 0.0.1304 | 16 / 5 | |
| 0.0.1301 | 16 / 5 | |
| 0.0.1297 | 16 / 5 | |
| 0.0.1286 | 16 / 5 | |
| 0.0.1285 | 16 / 5 | |
| 0.0.1284 | 16 / 5 | |
| 0.0.1257 | 16 / 5 | |
| 0.0.1256 | 16 / 5 | |
| 0.0.1232 | 18 / 5 | |
| 0.0.1228 | 18 / 5 | |
| 0.0.1189 | 18 / 5 | |
| 0.0.1188 | 18 / 5 | |
| 0.0.1187 | 18 / 5 | |
| 0.0.1132 | 18 / 5 | |
| 0.0.1035 | 12 / 5 | |
| 0.0.1002 | 12 / 5 | |
| 0.0.991 | 12 / 5 | |
| 0.0.988 | 12 / 6 | |
| 0.0.982 | 12 / 6 | |
| 0.0.975 | 12 / 6 | |
| 0.0.973 | 12 / 6 | |
| 0.0.970 | 12 / 6 | |
| 0.0.969 | 12 / 6 | |
| 0.0.895 | 11 / 6 | |
| 0.0.894 | 10 / 6 | |
| 0.0.893 | 10 / 6 | |
| 0.0.892 | 10 / 6 | |
| 0.0.891 | 10 / 6 | |
| 0.0.890 | 10 / 6 | |
| 0.0.889 | 10 / 6 | |
| 0.0.888 | 10 / 6 | |
| 0.0.887 | 10 / 6 | |
| 0.0.886 | 10 / 6 | |
| 0.0.885 | 10 / 6 | |
| 0.0.884 | 10 / 6 | |
| 0.0.883 | 10 / 6 | |
| 0.0.882 | 10 / 6 | |
| 0.0.881 | 10 / 6 | |
| 0.0.880 | 10 / 6 | |
| 0.0.879 | 10 / 6 | |
| 0.0.878 | 10 / 6 | |
| 0.0.877 | 10 / 6 | |
| 0.0.876 | 10 / 6 | |
| 0.0.875 | 10 / 6 | |
| 0.0.874 | 10 / 6 | |
| 0.0.873 | 10 / 6 | |
| 0.0.872 | 10 / 6 | |
| 0.0.871 | 10 / 6 | |
| 0.0.870 | 10 / 6 | |
| 0.0.869 | 10 / 6 | |
| 0.0.868 | 10 / 6 | |
| 0.0.867 | 10 / 6 | |
| 0.0.866 | 10 / 6 | |
| 0.0.865 | 9 / 6 | |
| 0.0.864 | 9 / 6 | |
| 0.0.863 | 9 / 6 |
v0.0.1351
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1349
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.1035
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1002
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.991
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.988
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.982
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.975
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.973
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.970
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.969
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.895
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.894
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.893
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.892
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.891
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.890
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.889
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.888
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.887
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.886
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.885
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.884
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.883
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.882
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.881
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.880
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.879
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.878
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.877
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.876
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.875
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.874
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.873
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.872
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.871
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.870
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.869
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.868
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.867
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.866
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.865
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.864
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.863
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.