@teambit/component-log
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.constants | AI (dependencies): First-party teambit monorepo dependency, not third-party unvetted code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party teambit package and semver; benign monorepo pattern. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo lockstep publishing pattern typical for Teambit packages, not malicious automation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 1562-day history; missing description is metadata gap, not malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is infrastructure gap; stable across this package's long history. | ai | |
| dependencies | unvetted-dep:@teambit/scope.remotes | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/graph.cleargraph | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy-component-log | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.component-diff | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/toolbox.path.path | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/objects | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Sibling @teambit monorepo dep; stable false positive for this package family. | ai |
Versions (showing 100 of 431)
| Version | Deps | Published |
|---|---|---|
| 1.0.944 | 17 / 5 | |
| 1.0.943 | 17 / 5 | |
| 1.0.942 | 17 / 5 | |
| 1.0.941 | 17 / 5 | |
| 1.0.940 | 17 / 5 | |
| 1.0.939 | 17 / 5 | |
| 1.0.938 | 17 / 5 | |
| 1.0.937 | 17 / 5 | |
| 1.0.936 | 17 / 5 | |
| 1.0.935 | 17 / 5 | |
| 1.0.934 | 17 / 5 | |
| 1.0.933 | 17 / 5 | |
| 1.0.932 | 17 / 5 | |
| 1.0.931 | 17 / 5 | |
| 1.0.930 | 17 / 5 | |
| 1.0.929 | 17 / 5 | |
| 1.0.928 | 17 / 5 | |
| 1.0.927 | 17 / 5 | |
| 1.0.926 | 17 / 5 | |
| 1.0.925 | 17 / 5 | |
| 1.0.924 | 17 / 5 | |
| 1.0.923 | 17 / 5 | |
| 1.0.922 | 17 / 5 | |
| 1.0.921 | 17 / 5 | |
| 1.0.920 | 17 / 5 | |
| 1.0.919 | 17 / 5 | |
| 1.0.918 | 17 / 5 | |
| 1.0.917 | 17 / 5 | |
| 1.0.916 | 17 / 5 | |
| 1.0.915 | 17 / 5 | |
| 1.0.914 | 17 / 5 | |
| 1.0.913 | 17 / 5 | |
| 1.0.912 | 17 / 5 | |
| 1.0.911 | 17 / 5 | |
| 1.0.910 | 17 / 5 | |
| 1.0.909 | 17 / 5 | |
| 1.0.907 | 17 / 5 | |
| 1.0.906 | 17 / 5 | |
| 1.0.905 | 17 / 5 | |
| 1.0.904 | 17 / 5 | |
| 1.0.903 | 17 / 5 | |
| 1.0.902 | 17 / 5 | |
| 1.0.901 | 17 / 5 | |
| 1.0.900 | 17 / 5 | |
| 1.0.899 | 17 / 5 | |
| 1.0.898 | 17 / 5 | |
| 1.0.897 | 17 / 5 | |
| 1.0.896 | 17 / 5 | |
| 1.0.895 | 17 / 5 | |
| 1.0.894 | 17 / 5 | |
| 1.0.893 | 17 / 5 | |
| 1.0.892 | 17 / 5 | |
| 1.0.891 | 17 / 5 | |
| 1.0.890 | 17 / 5 | |
| 1.0.889 | 17 / 5 | |
| 1.0.888 | 17 / 5 | |
| 1.0.887 | 17 / 5 | |
| 1.0.886 | 17 / 5 | |
| 1.0.885 | 17 / 5 | |
| 1.0.884 | 17 / 5 | |
| 1.0.883 | 17 / 5 | |
| 1.0.882 | 17 / 5 | |
| 1.0.881 | 17 / 5 | |
| 1.0.880 | 17 / 5 | |
| 1.0.879 | 17 / 5 | |
| 1.0.878 | 17 / 5 | |
| 1.0.877 | 17 / 5 | |
| 1.0.876 | 17 / 5 | |
| 1.0.875 | 17 / 5 | |
| 1.0.874 | 17 / 5 | |
| 1.0.873 | 17 / 5 | |
| 1.0.872 | 17 / 5 | |
| 1.0.871 | 17 / 5 | |
| 1.0.870 | 17 / 5 | |
| 1.0.869 | 17 / 5 | |
| 1.0.868 | 17 / 5 | |
| 1.0.867 | 17 / 5 | |
| 1.0.866 | 17 / 5 | |
| 1.0.865 | 17 / 5 | |
| 1.0.864 | 17 / 5 | |
| 1.0.863 | 17 / 5 | |
| 1.0.862 | 17 / 5 | |
| 1.0.861 | 17 / 5 | |
| 1.0.860 | 17 / 5 | |
| 1.0.859 | 17 / 5 | |
| 1.0.858 | 17 / 5 | |
| 1.0.857 | 17 / 5 | |
| 1.0.856 | 17 / 5 | |
| 1.0.855 | 17 / 5 | |
| 1.0.854 | 17 / 5 | |
| 1.0.853 | 17 / 5 | |
| 1.0.852 | 17 / 5 | |
| 1.0.851 | 17 / 5 | |
| 1.0.850 | 17 / 5 | |
| 1.0.849 | 17 / 5 | |
| 1.0.848 | 17 / 5 | |
| 1.0.847 | 17 / 5 | |
| 1.0.846 | 17 / 5 | |
| 1.0.845 | 17 / 5 | |
| 1.0.844 | 17 / 5 |
v1.0.944
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.939
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.938
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.931
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.924
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.923
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.922
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.921
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.920
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.919
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.918
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.917
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.916
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.915
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.914
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.913
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.912
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.911
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.910
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.909
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.907
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.906
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.905
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.904
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.903
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.902
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.901
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.900
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.899
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.898
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.897
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.896
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.895
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.894
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.893
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.892
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.891
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.890
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.889
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.888
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.887
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.886
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.885
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.884
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.883
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.882
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.881
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.880
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.879
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.878
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.877
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.876
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.875
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.874
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.873
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.872
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.871
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.870
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.869
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.868
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.867
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.866
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.865
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v1.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.
v1.0.862
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.861
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.860
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.859
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.858
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.857
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.856
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.855
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.854
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.853
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.852
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.851
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.850
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.849
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.848
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.847
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.846
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.845
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.844
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.