@teambit/command-bar
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/workspace.ui.use-workspace-mode | AI (dependencies): First-party teambit monorepo dependency, consistent with package's ecosystem. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party @teambit package, typical for this monorepo. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo lockstep releases publish many @teambit packages in quick succession; benign pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 2900+ versions; missing description is stable metadata pattern. | ai | |
| provenance | no-provenance | AI (provenance): Long-standing package; provenance absence is consistent across versions. | ai | |
| dependencies | unvetted-dep:@teambit/base-ui.text.muted-text | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/explorer.ui.command-bar | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/ui-foundation.ui.keycap | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/ui | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/ui-foundation.ui.is-browser | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/design.buttons.action-button | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/design.ui.styles.ellipsis | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/pubsub | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai | |
| dependencies | unvetted-dep:@teambit/react-router | AI (dependencies): Sibling @teambit/* package from same monorepo; unvetted status is a registry gap, not a risk. | ai |
Versions (showing 100 of 494)
| Version | Deps | Published |
|---|---|---|
| 1.0.903 | 15 / 6 | |
| 1.0.902 | 15 / 6 | |
| 1.0.900 | 15 / 6 | |
| 1.0.899 | 15 / 6 | |
| 1.0.897 | 15 / 6 | |
| 1.0.896 | 15 / 6 | |
| 1.0.895 | 15 / 6 | |
| 1.0.894 | 15 / 6 | |
| 1.0.893 | 15 / 6 | |
| 1.0.890 | 15 / 6 | |
| 1.0.889 | 15 / 6 | |
| 1.0.888 | 15 / 6 | |
| 1.0.887 | 15 / 6 | |
| 1.0.886 | 15 / 6 | |
| 1.0.885 | 15 / 6 | |
| 1.0.884 | 15 / 6 | |
| 1.0.883 | 15 / 6 | |
| 1.0.882 | 15 / 6 | |
| 1.0.881 | 15 / 6 | |
| 1.0.879 | 15 / 6 | |
| 1.0.878 | 15 / 6 | |
| 1.0.877 | 15 / 6 | |
| 1.0.876 | 15 / 6 | |
| 1.0.875 | 15 / 6 | |
| 1.0.874 | 15 / 6 | |
| 1.0.873 | 15 / 6 | |
| 1.0.872 | 15 / 6 | |
| 1.0.871 | 15 / 6 | |
| 1.0.870 | 15 / 6 | |
| 1.0.869 | 15 / 6 | |
| 1.0.868 | 15 / 6 | |
| 1.0.867 | 15 / 6 | |
| 1.0.866 | 15 / 6 | |
| 1.0.865 | 15 / 6 | |
| 1.0.864 | 15 / 6 | |
| 1.0.863 | 15 / 6 | |
| 1.0.862 | 15 / 6 | |
| 1.0.861 | 15 / 6 | |
| 1.0.860 | 15 / 6 | |
| 1.0.859 | 15 / 6 | |
| 1.0.856 | 15 / 6 | |
| 1.0.855 | 15 / 6 | |
| 1.0.854 | 15 / 6 | |
| 1.0.853 | 15 / 6 | |
| 1.0.852 | 15 / 6 | |
| 1.0.851 | 15 / 6 | |
| 1.0.850 | 15 / 6 | |
| 1.0.849 | 15 / 6 | |
| 1.0.848 | 15 / 6 | |
| 1.0.847 | 15 / 6 | |
| 1.0.846 | 15 / 6 | |
| 1.0.845 | 15 / 6 | |
| 1.0.844 | 15 / 6 | |
| 1.0.842 | 15 / 6 | |
| 1.0.841 | 15 / 6 | |
| 1.0.840 | 15 / 6 | |
| 1.0.839 | 15 / 6 | |
| 1.0.838 | 15 / 6 | |
| 1.0.836 | 15 / 6 | |
| 1.0.835 | 15 / 6 | |
| 1.0.833 | 15 / 6 | |
| 1.0.832 | 15 / 6 | |
| 1.0.831 | 15 / 6 | |
| 1.0.830 | 15 / 6 | |
| 1.0.828 | 15 / 6 | |
| 1.0.826 | 15 / 6 | |
| 1.0.825 | 15 / 6 | |
| 1.0.824 | 15 / 6 | |
| 1.0.823 | 15 / 6 | |
| 1.0.820 | 15 / 6 | |
| 1.0.817 | 15 / 6 | |
| 1.0.816 | 15 / 6 | |
| 1.0.814 | 15 / 6 | |
| 1.0.811 | 15 / 6 | |
| 1.0.810 | 15 / 6 | |
| 1.0.808 | 15 / 6 | |
| 1.0.805 | 15 / 6 | |
| 1.0.804 | 15 / 6 | |
| 1.0.802 | 15 / 6 | |
| 1.0.800 | 16 / 6 | |
| 1.0.799 | 16 / 6 | |
| 1.0.798 | 16 / 6 | |
| 1.0.796 | 16 / 6 | |
| 1.0.795 | 16 / 6 | |
| 1.0.794 | 16 / 6 | |
| 1.0.793 | 16 / 6 | |
| 1.0.792 | 16 / 6 | |
| 1.0.791 | 16 / 6 | |
| 1.0.790 | 16 / 6 | |
| 1.0.789 | 16 / 6 | |
| 1.0.788 | 16 / 6 | |
| 1.0.787 | 16 / 6 | |
| 1.0.786 | 16 / 6 | |
| 1.0.784 | 16 / 6 | |
| 1.0.783 | 16 / 6 | |
| 1.0.782 | 16 / 6 | |
| 1.0.781 | 16 / 6 | |
| 1.0.779 | 16 / 6 | |
| 1.0.778 | 16 / 6 | |
| 1.0.777 | 16 / 6 |
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.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.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.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.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.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.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.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.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.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.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.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.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.
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.811
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.810
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.808
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.805
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.802
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.799
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.798
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.796
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.792
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.791
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.790
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.789
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.788
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.787
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.784
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.783
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.781
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.779
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.778
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.