@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.1060 | 15 / 6 | |
| 1.0.1056 | 15 / 6 | |
| 1.0.1055 | 15 / 6 | |
| 1.0.1052 | 15 / 6 | |
| 1.0.1051 | 15 / 6 | |
| 1.0.1047 | 15 / 6 | |
| 1.0.1044 | 15 / 6 | |
| 1.0.1041 | 15 / 6 | |
| 1.0.1038 | 15 / 6 | |
| 1.0.1033 | 15 / 6 | |
| 1.0.1028 | 15 / 6 | |
| 1.0.1026 | 15 / 6 | |
| 1.0.1021 | 15 / 6 | |
| 1.0.1020 | 15 / 6 | |
| 1.0.1018 | 15 / 6 | |
| 1.0.1017 | 15 / 6 | |
| 1.0.1016 | 15 / 6 | |
| 1.0.1014 | 15 / 6 | |
| 1.0.1012 | 15 / 6 | |
| 1.0.1008 | 15 / 6 | |
| 1.0.1007 | 15 / 6 | |
| 1.0.1005 | 15 / 6 | |
| 1.0.1002 | 15 / 6 | |
| 1.0.999 | 15 / 6 | |
| 1.0.997 | 15 / 6 | |
| 1.0.995 | 15 / 6 | |
| 1.0.994 | 15 / 6 | |
| 1.0.992 | 15 / 6 | |
| 1.0.991 | 15 / 6 | |
| 1.0.989 | 15 / 6 | |
| 1.0.988 | 15 / 6 | |
| 1.0.987 | 15 / 6 | |
| 1.0.985 | 15 / 6 | |
| 1.0.982 | 15 / 6 | |
| 1.0.980 | 15 / 6 | |
| 1.0.979 | 15 / 6 | |
| 1.0.978 | 15 / 6 | |
| 1.0.977 | 15 / 6 | |
| 1.0.976 | 15 / 6 | |
| 1.0.975 | 15 / 6 | |
| 1.0.974 | 15 / 6 | |
| 1.0.972 | 15 / 6 | |
| 1.0.971 | 15 / 6 | |
| 1.0.970 | 15 / 6 | |
| 1.0.969 | 15 / 6 | |
| 1.0.968 | 15 / 6 | |
| 1.0.967 | 15 / 6 | |
| 1.0.966 | 15 / 6 | |
| 1.0.965 | 15 / 6 | |
| 1.0.964 | 15 / 6 | |
| 1.0.963 | 15 / 6 | |
| 1.0.962 | 15 / 6 | |
| 1.0.961 | 15 / 6 | |
| 1.0.960 | 15 / 6 | |
| 1.0.958 | 15 / 6 | |
| 1.0.957 | 15 / 6 | |
| 1.0.956 | 15 / 6 | |
| 1.0.955 | 15 / 6 | |
| 1.0.954 | 15 / 6 | |
| 1.0.953 | 15 / 6 | |
| 1.0.952 | 15 / 6 | |
| 1.0.951 | 15 / 6 | |
| 1.0.950 | 15 / 6 | |
| 1.0.949 | 15 / 6 | |
| 1.0.948 | 15 / 6 | |
| 1.0.947 | 15 / 6 | |
| 1.0.946 | 15 / 6 | |
| 1.0.945 | 15 / 6 | |
| 1.0.944 | 15 / 6 | |
| 1.0.943 | 15 / 6 | |
| 1.0.942 | 15 / 6 | |
| 1.0.941 | 15 / 6 | |
| 1.0.940 | 15 / 6 | |
| 1.0.938 | 15 / 6 | |
| 1.0.937 | 15 / 6 | |
| 1.0.936 | 15 / 6 | |
| 1.0.935 | 15 / 6 | |
| 1.0.934 | 15 / 6 | |
| 1.0.933 | 15 / 6 | |
| 1.0.932 | 15 / 6 | |
| 1.0.931 | 15 / 6 | |
| 1.0.930 | 15 / 6 | |
| 1.0.929 | 15 / 6 | |
| 1.0.928 | 15 / 6 | |
| 1.0.927 | 15 / 6 | |
| 1.0.926 | 15 / 6 | |
| 1.0.925 | 15 / 6 | |
| 1.0.924 | 15 / 6 | |
| 1.0.923 | 15 / 6 | |
| 1.0.922 | 15 / 6 | |
| 1.0.921 | 15 / 6 | |
| 1.0.916 | 15 / 6 | |
| 1.0.915 | 15 / 6 | |
| 1.0.913 | 15 / 6 | |
| 1.0.912 | 15 / 6 | |
| 1.0.910 | 15 / 6 | |
| 1.0.909 | 15 / 6 | |
| 1.0.907 | 15 / 6 | |
| 1.0.906 | 15 / 6 | |
| 1.0.905 | 15 / 6 |
v1.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1056
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1055
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1052
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1051
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1047
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1044
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1041
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.992
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.989
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.988
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.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.975
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.965
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.957
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.953
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.950
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.945
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.942
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.930
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.927
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.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.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.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.