@teambit/code
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established package with 2724 versions; missing description is stable pattern, not malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is infrastructure choice, not security risk for this established package. | ai | |
| dependencies | unvetted-dep:@teambit/ui-foundation.ui.menu-widget-icon | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@teambit/code.ui.utils.get-file-icon | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@teambit/code.ui.code-compare-section | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@teambit/code.ui.code-editor | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@teambit/code.ui.code-compare | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@teambit/code.ui.code-tab-page | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@teambit/base-ui.constants.storage | AI (dependencies): Internal teambit ecosystem dependency; stable pattern across all versions of this package. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @teambit/code package; not a typosquat of zod — different namespace and purpose entirely. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @teambit/code package; not a typosquat of cors — different namespace and purpose entirely. | ai |
Versions (showing 100 of 406)
| Version | Deps | Published |
|---|---|---|
| 1.0.916 | 11 / 2 | |
| 1.0.915 | 11 / 2 | |
| 1.0.914 | 11 / 2 | |
| 1.0.913 | 11 / 2 | |
| 1.0.912 | 11 / 2 | |
| 1.0.911 | 11 / 2 | |
| 1.0.910 | 11 / 2 | |
| 1.0.909 | 11 / 2 | |
| 1.0.907 | 11 / 2 | |
| 1.0.906 | 11 / 2 | |
| 1.0.905 | 11 / 2 | |
| 1.0.904 | 11 / 2 | |
| 1.0.903 | 11 / 2 | |
| 1.0.902 | 11 / 2 | |
| 1.0.901 | 11 / 2 | |
| 1.0.900 | 11 / 2 | |
| 1.0.899 | 11 / 2 | |
| 1.0.898 | 11 / 2 | |
| 1.0.897 | 11 / 2 | |
| 1.0.896 | 11 / 2 | |
| 1.0.895 | 11 / 2 | |
| 1.0.894 | 11 / 2 | |
| 1.0.893 | 11 / 2 | |
| 1.0.892 | 11 / 2 | |
| 1.0.891 | 11 / 2 | |
| 1.0.890 | 11 / 2 | |
| 1.0.889 | 11 / 2 | |
| 1.0.888 | 11 / 2 | |
| 1.0.887 | 11 / 2 | |
| 1.0.886 | 11 / 2 | |
| 1.0.885 | 11 / 2 | |
| 1.0.884 | 11 / 2 | |
| 1.0.883 | 11 / 2 | |
| 1.0.882 | 11 / 2 | |
| 1.0.881 | 11 / 2 | |
| 1.0.880 | 11 / 2 | |
| 1.0.879 | 11 / 2 | |
| 1.0.878 | 11 / 2 | |
| 1.0.877 | 11 / 2 | |
| 1.0.876 | 11 / 2 | |
| 1.0.875 | 11 / 2 | |
| 1.0.874 | 11 / 2 | |
| 1.0.873 | 11 / 2 | |
| 1.0.872 | 11 / 2 | |
| 1.0.871 | 11 / 2 | |
| 1.0.870 | 11 / 2 | |
| 1.0.869 | 11 / 2 | |
| 1.0.868 | 11 / 2 | |
| 1.0.867 | 11 / 2 | |
| 1.0.866 | 11 / 2 | |
| 1.0.865 | 11 / 2 | |
| 1.0.864 | 11 / 2 | |
| 1.0.863 | 11 / 2 | |
| 1.0.862 | 11 / 2 | |
| 1.0.861 | 11 / 2 | |
| 1.0.860 | 11 / 2 | |
| 1.0.859 | 11 / 2 | |
| 1.0.858 | 11 / 2 | |
| 1.0.857 | 11 / 2 | |
| 1.0.856 | 11 / 2 | |
| 1.0.855 | 11 / 2 | |
| 1.0.854 | 11 / 2 | |
| 1.0.853 | 11 / 2 | |
| 1.0.852 | 11 / 2 | |
| 1.0.851 | 11 / 2 | |
| 1.0.850 | 11 / 2 | |
| 1.0.849 | 11 / 2 | |
| 1.0.848 | 11 / 2 | |
| 1.0.847 | 11 / 2 | |
| 1.0.846 | 11 / 2 | |
| 1.0.845 | 11 / 2 | |
| 1.0.844 | 11 / 2 | |
| 1.0.843 | 11 / 2 | |
| 1.0.842 | 11 / 2 | |
| 1.0.841 | 11 / 2 | |
| 1.0.840 | 11 / 2 | |
| 1.0.839 | 11 / 2 | |
| 1.0.838 | 11 / 2 | |
| 1.0.837 | 11 / 2 | |
| 1.0.836 | 11 / 2 | |
| 1.0.835 | 11 / 2 | |
| 1.0.834 | 11 / 2 | |
| 1.0.833 | 11 / 2 | |
| 1.0.832 | 11 / 2 | |
| 1.0.831 | 11 / 2 | |
| 1.0.830 | 11 / 2 | |
| 1.0.829 | 11 / 2 | |
| 1.0.828 | 11 / 2 | |
| 1.0.827 | 11 / 2 | |
| 1.0.826 | 11 / 2 | |
| 1.0.825 | 11 / 2 | |
| 1.0.824 | 11 / 2 | |
| 1.0.823 | 11 / 2 | |
| 1.0.822 | 11 / 2 | |
| 1.0.821 | 11 / 2 | |
| 1.0.820 | 11 / 2 | |
| 1.0.819 | 11 / 2 | |
| 1.0.818 | 11 / 2 | |
| 1.0.817 | 11 / 2 | |
| 1.0.816 | 11 / 2 |
v1.0.916
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.915
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.914
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.913
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.912
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.911
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.910
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.909
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.907
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.906
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.905
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.904
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.903
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.902
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.901
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.900
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.899
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.898
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.897
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.896
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.895
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.894
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.893
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.892
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.891
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.890
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.889
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.888
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.887
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.886
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.885
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.884
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.883
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.882
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.881
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.880
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.879
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.878
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.877
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.876
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.0.843
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.842
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.841
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.840
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.839
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.838
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.837
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.836
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.835
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.834
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.833
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.832
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.831
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.830
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.829
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.828
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.827
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.826
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.825
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.824
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.823
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.822
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.821
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.820
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.819
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.818
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.817
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.816
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.