@teambit/harmony-ui-app
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/harmony | AI (dependencies): First-party teambit dependency; stable across all versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established teambit ecosystem package; missing description is a cosmetic issue, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Teambit packages consistently lack provenance attestation; not a risk indicator for this publisher. | ai |
Versions (showing 100 of 394)
| Version | Deps | Published |
|---|---|---|
| 1.0.1007 | 6 / 2 | |
| 1.0.1006 | 6 / 2 | |
| 1.0.1005 | 6 / 2 | |
| 1.0.1004 | 6 / 2 | |
| 1.0.1003 | 6 / 2 | |
| 1.0.1002 | 6 / 2 | |
| 1.0.1001 | 6 / 2 | |
| 1.0.1000 | 6 / 2 | |
| 1.0.999 | 6 / 2 | |
| 1.0.998 | 6 / 2 | |
| 1.0.997 | 6 / 2 | |
| 1.0.996 | 6 / 2 | |
| 1.0.995 | 6 / 2 | |
| 1.0.994 | 6 / 2 | |
| 1.0.993 | 6 / 2 | |
| 1.0.992 | 6 / 2 | |
| 1.0.991 | 6 / 2 | |
| 1.0.990 | 6 / 2 | |
| 1.0.989 | 6 / 2 | |
| 1.0.988 | 6 / 2 | |
| 1.0.987 | 6 / 2 | |
| 1.0.986 | 6 / 2 | |
| 1.0.985 | 6 / 2 | |
| 1.0.984 | 6 / 2 | |
| 1.0.983 | 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.975 | 6 / 2 | |
| 1.0.974 | 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.965 | 6 / 2 | |
| 1.0.964 | 6 / 2 | |
| 1.0.963 | 6 / 2 | |
| 1.0.962 | 6 / 2 | |
| 1.0.961 | 6 / 2 | |
| 1.0.960 | 6 / 2 | |
| 1.0.959 | 6 / 2 | |
| 1.0.958 | 6 / 2 | |
| 1.0.957 | 6 / 2 | |
| 1.0.956 | 6 / 2 | |
| 1.0.955 | 6 / 2 | |
| 1.0.954 | 6 / 2 | |
| 1.0.953 | 6 / 2 | |
| 1.0.952 | 6 / 2 | |
| 1.0.951 | 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.945 | 6 / 2 | |
| 1.0.944 | 6 / 2 | |
| 1.0.943 | 6 / 2 | |
| 1.0.942 | 6 / 2 | |
| 1.0.941 | 6 / 2 | |
| 1.0.940 | 6 / 2 | |
| 1.0.939 | 6 / 2 | |
| 1.0.938 | 6 / 2 | |
| 1.0.937 | 6 / 2 | |
| 1.0.936 | 6 / 2 | |
| 1.0.935 | 6 / 2 | |
| 1.0.934 | 6 / 2 | |
| 1.0.933 | 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.924 | 6 / 2 | |
| 1.0.923 | 6 / 2 | |
| 1.0.922 | 6 / 2 | |
| 1.0.921 | 6 / 2 | |
| 1.0.920 | 6 / 2 | |
| 1.0.919 | 6 / 2 | |
| 1.0.918 | 6 / 2 | |
| 1.0.917 | 6 / 2 | |
| 1.0.916 | 6 / 2 | |
| 1.0.915 | 6 / 2 | |
| 1.0.914 | 6 / 2 | |
| 1.0.913 | 6 / 2 | |
| 1.0.912 | 6 / 2 | |
| 1.0.911 | 6 / 2 | |
| 1.0.910 | 6 / 2 | |
| 1.0.909 | 6 / 2 | |
| 1.0.907 | 6 / 2 |
v1.0.1007
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1006
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1005
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1004
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1003
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1002
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1001
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1000
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.999
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.998
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.997
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.996
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.995
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.994
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.993
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.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.988
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.986
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.984
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.983
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.975
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.974
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.924
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.922
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.921
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.918
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.917
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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. 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.