@teambit/changelog
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/component.ui.version-block | AI (dependencies): Internal @teambit scoped dependency; consistent with this package's established monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component.instructions.exporting-components | AI (dependencies): Internal @teambit scoped dependency; consistent with this package's established monorepo publishing pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established teambit component package; missing description is a known pattern across their published components. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes thousands of packages without provenance; consistent pattern, not a risk signal here. | ai |
Versions (showing 51 of 799)
| Version | Deps | Published |
|---|---|---|
| 1.0.1077 | 11 / 3 | |
| 1.0.1076 | 11 / 3 | |
| 1.0.1075 | 11 / 3 | |
| 1.0.1074 | 11 / 3 | |
| 1.0.1073 | 11 / 3 | |
| 1.0.1072 | 11 / 3 | |
| 1.0.1071 | 11 / 3 | |
| 1.0.1070 | 11 / 3 | |
| 1.0.1069 | 11 / 3 | |
| 1.0.1068 | 11 / 3 | |
| 1.0.1067 | 11 / 3 | |
| 1.0.1066 | 11 / 3 | |
| 1.0.1065 | 11 / 3 | |
| 1.0.1064 | 11 / 3 | |
| 1.0.1063 | 11 / 3 | |
| 1.0.1062 | 11 / 3 | |
| 1.0.1061 | 11 / 3 | |
| 1.0.1060 | 11 / 3 | |
| 1.0.1059 | 11 / 3 | |
| 1.0.1058 | 11 / 3 | |
| 1.0.1057 | 11 / 3 | |
| 1.0.1056 | 11 / 3 | |
| 1.0.1055 | 11 / 3 | |
| 1.0.1054 | 11 / 3 | |
| 1.0.1053 | 11 / 3 | |
| 1.0.1052 | 11 / 3 | |
| 1.0.1051 | 11 / 3 | |
| 1.0.1050 | 11 / 3 | |
| 1.0.1049 | 11 / 3 | |
| 1.0.1048 | 11 / 3 | |
| 1.0.1047 | 11 / 3 | |
| 1.0.1046 | 11 / 3 | |
| 1.0.1045 | 11 / 3 | |
| 1.0.1044 | 11 / 3 | |
| 1.0.1043 | 11 / 3 | |
| 1.0.1042 | 11 / 3 | |
| 1.0.1041 | 11 / 3 | |
| 1.0.1040 | 11 / 3 | |
| 1.0.1039 | 11 / 3 | |
| 1.0.1038 | 11 / 3 | |
| 1.0.1037 | 11 / 3 | |
| 1.0.1036 | 11 / 3 | |
| 1.0.1035 | 11 / 3 | |
| 1.0.1034 | 11 / 3 | |
| 1.0.1033 | 11 / 3 | |
| 1.0.1032 | 11 / 3 | |
| 1.0.1031 | 11 / 3 | |
| 1.0.1030 | 11 / 3 | |
| 1.0.1029 | 11 / 3 | |
| 1.0.1028 | 11 / 3 | |
| 1.0.1027 | 11 / 3 |
v1.0.1077
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1076
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1075
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1074
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1073
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1072
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1071
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1070
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1069
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1068
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1067
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1066
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1065
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1064
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1063
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1062
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1061
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1060
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1059
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1058
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1057
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.1054
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1053
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.1050
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1049
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1048
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.1046
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1045
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.1043
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1042
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.1040
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.