@teambit/diagnostic
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/bit.get-bit-version | AI (dependencies): First-party teambit package; stable dependency across versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Auto-generated component package from teambit/bit monorepo; missing description is a stable pattern across all @teambit/* packages. | ai | |
| provenance | no-provenance | AI (provenance): teambit/bit publishes thousands of component packages without Sigstore provenance; stable pattern for this publisher. | ai |
Versions (showing 100 of 169)
| Version | Deps | Published |
|---|---|---|
| 1.0.993 | 6 / 2 | |
| 1.0.991 | 6 / 2 | |
| 1.0.990 | 6 / 2 | |
| 1.0.989 | 6 / 2 | |
| 1.0.987 | 6 / 2 | |
| 1.0.985 | 6 / 2 | |
| 1.0.982 | 6 / 2 | |
| 1.0.981 | 6 / 2 | |
| 1.0.980 | 6 / 2 | |
| 1.0.979 | 6 / 2 | |
| 1.0.978 | 6 / 2 | |
| 1.0.977 | 6 / 2 | |
| 1.0.976 | 6 / 2 | |
| 1.0.973 | 6 / 2 | |
| 1.0.972 | 6 / 2 | |
| 1.0.971 | 6 / 2 | |
| 1.0.970 | 6 / 2 | |
| 1.0.969 | 6 / 2 | |
| 1.0.968 | 6 / 2 | |
| 1.0.967 | 6 / 2 | |
| 1.0.966 | 6 / 2 | |
| 1.0.962 | 6 / 2 | |
| 1.0.960 | 6 / 2 | |
| 1.0.959 | 6 / 2 | |
| 1.0.957 | 6 / 2 | |
| 1.0.955 | 6 / 2 | |
| 1.0.954 | 6 / 2 | |
| 1.0.953 | 6 / 2 | |
| 1.0.952 | 6 / 2 | |
| 1.0.950 | 6 / 2 | |
| 1.0.949 | 6 / 2 | |
| 1.0.948 | 6 / 2 | |
| 1.0.947 | 6 / 2 | |
| 1.0.946 | 6 / 2 | |
| 1.0.944 | 6 / 2 | |
| 1.0.943 | 6 / 2 | |
| 1.0.942 | 6 / 2 | |
| 1.0.941 | 6 / 2 | |
| 1.0.939 | 6 / 2 | |
| 1.0.938 | 6 / 2 | |
| 1.0.937 | 6 / 2 | |
| 1.0.935 | 6 / 2 | |
| 1.0.934 | 6 / 2 | |
| 1.0.932 | 6 / 2 | |
| 1.0.931 | 6 / 2 | |
| 1.0.930 | 6 / 2 | |
| 1.0.929 | 6 / 2 | |
| 1.0.928 | 6 / 2 | |
| 1.0.927 | 6 / 2 | |
| 1.0.926 | 6 / 2 | |
| 1.0.925 | 6 / 2 | |
| 1.0.923 | 6 / 2 | |
| 1.0.919 | 6 / 2 | |
| 1.0.915 | 6 / 2 | |
| 1.0.913 | 6 / 2 | |
| 1.0.910 | 6 / 2 | |
| 1.0.906 | 6 / 2 | |
| 1.0.901 | 6 / 2 | |
| 1.0.899 | 6 / 2 | |
| 1.0.896 | 6 / 2 | |
| 1.0.889 | 6 / 2 | |
| 1.0.886 | 6 / 2 | |
| 1.0.885 | 6 / 2 | |
| 1.0.881 | 6 / 2 | |
| 1.0.878 | 6 / 2 | |
| 1.0.871 | 6 / 2 | |
| 1.0.869 | 6 / 2 | |
| 1.0.866 | 6 / 2 | |
| 1.0.862 | 6 / 2 | |
| 1.0.860 | 6 / 2 | |
| 1.0.856 | 6 / 2 | |
| 1.0.855 | 6 / 2 | |
| 1.0.853 | 6 / 2 | |
| 1.0.851 | 6 / 2 | |
| 1.0.848 | 6 / 2 | |
| 1.0.845 | 6 / 2 | |
| 1.0.843 | 6 / 2 | |
| 1.0.840 | 6 / 2 | |
| 1.0.839 | 6 / 2 | |
| 1.0.837 | 6 / 2 | |
| 1.0.833 | 6 / 2 | |
| 1.0.831 | 6 / 2 | |
| 1.0.826 | 6 / 2 | |
| 1.0.824 | 6 / 2 | |
| 1.0.820 | 6 / 2 | |
| 1.0.816 | 6 / 2 | |
| 1.0.814 | 6 / 2 | |
| 1.0.813 | 6 / 2 | |
| 1.0.809 | 6 / 2 | |
| 1.0.806 | 6 / 2 | |
| 1.0.804 | 6 / 2 | |
| 1.0.800 | 6 / 2 | |
| 1.0.797 | 6 / 2 | |
| 1.0.795 | 6 / 2 | |
| 1.0.794 | 6 / 2 | |
| 1.0.793 | 6 / 2 | |
| 1.0.786 | 6 / 2 | |
| 1.0.782 | 6 / 2 | |
| 1.0.780 | 6 / 2 | |
| 1.0.777 | 6 / 2 |
v1.0.993
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.991
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.990
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.989
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.987
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.985
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.982
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.981
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.980
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.979
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.978
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.977
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.976
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.973
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.972
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.971
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.970
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.969
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.967
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.966
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.962
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.959
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.943
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.937
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.
v1.0.814
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.813
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.809
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.806
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.804
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.800
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.797
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.795
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.794
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.793
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.786
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.782
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.780
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.777
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.