← Home

@teambit/panels

npm Repository Homepage
100
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

teambit-ownershohamgiladdavidfirstranm8guysaaritaymendelerezbitjoshk2redigmayona007

Keywords

bitbit-aspectbit-core-aspectcomponentscollaborationweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): davidfirst is a long-standing trusted publisher (178 approved, 0 rejected) within the teambit ecosystem. ai
npm-metadata no-description AI (npm-metadata): Auto-generated @teambit component packages routinely omit descriptions; stable pattern across 1500+ versions. ai
provenance no-provenance AI (provenance): teambit publishes hundreds of packages without provenance; consistent across the ecosystem. ai

Versions (showing 100 of 474)

Version Deps Published
0.0.1255 4 / 4
0.0.1254 4 / 4
0.0.1253 4 / 4
0.0.1252 4 / 4
0.0.1251 4 / 4
0.0.1250 4 / 4
0.0.1249 4 / 4
0.0.1248 4 / 4
0.0.1247 4 / 4
0.0.1246 4 / 4
0.0.1245 4 / 4
0.0.1244 4 / 4
0.0.1243 4 / 4
0.0.1242 4 / 4
0.0.1241 4 / 4
0.0.1240 4 / 4
0.0.1239 4 / 4
0.0.1238 4 / 4
0.0.1237 4 / 4
0.0.1236 4 / 4
0.0.1235 4 / 4
0.0.1234 4 / 4
0.0.1233 4 / 4
0.0.1232 4 / 4
0.0.1231 4 / 4
0.0.1230 4 / 4
0.0.1229 4 / 4
0.0.1228 4 / 4
0.0.1227 4 / 4
0.0.1226 4 / 4
0.0.1225 4 / 4
0.0.1224 4 / 4
0.0.1223 4 / 4
0.0.1222 4 / 4
0.0.1221 4 / 4
0.0.1220 4 / 4
0.0.1219 4 / 4
0.0.1218 4 / 4
0.0.1217 4 / 4
0.0.1216 4 / 4
0.0.1215 4 / 4
0.0.1214 4 / 4
0.0.1213 4 / 4
0.0.1212 4 / 4
0.0.1211 4 / 4
0.0.1210 4 / 4
0.0.1209 4 / 4
0.0.1208 4 / 4
0.0.1207 4 / 4
0.0.1206 4 / 4
0.0.1205 4 / 4
0.0.1204 4 / 4
0.0.1203 4 / 4
0.0.1202 4 / 4
0.0.1201 4 / 4
0.0.1200 4 / 4
0.0.1199 4 / 4
0.0.1198 4 / 4
0.0.1197 4 / 4
0.0.1196 4 / 4
0.0.1195 4 / 4
0.0.1194 4 / 4
0.0.1193 4 / 4
0.0.1192 4 / 4
0.0.1191 4 / 4
0.0.1190 4 / 4
0.0.1189 4 / 4
0.0.1187 4 / 4
0.0.1185 4 / 4
0.0.1183 4 / 4
0.0.1181 4 / 4
0.0.1179 4 / 4
0.0.1177 4 / 4
0.0.1175 4 / 4
0.0.1173 4 / 4
0.0.1171 4 / 4
0.0.1169 4 / 4
0.0.1167 4 / 4
0.0.1166 4 / 4
0.0.1165 4 / 4
0.0.1164 4 / 4
0.0.1163 4 / 4
0.0.1162 4 / 4
0.0.1161 4 / 4
0.0.1160 4 / 4
0.0.1159 4 / 4
0.0.1158 4 / 4
0.0.1157 4 / 4
0.0.1156 4 / 4
0.0.1155 4 / 4
0.0.1154 4 / 4
0.0.1153 4 / 4
0.0.1152 4 / 4
0.0.1151 4 / 4
0.0.1150 4 / 4
0.0.1149 4 / 4
0.0.1148 4 / 4
0.0.1147 4 / 4
0.0.1146 4 / 4
0.0.1145 4 / 4
Showing 100 of 474 Next page →

v0.0.1187

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1185

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1183

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1181

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1179

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1177

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1175

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1173

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1171

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1169

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1167

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1166

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1165

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1164

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1163

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1162

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1161

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1160

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1159

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1158

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1157

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1156

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1155

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1154

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1153

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1152

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1151

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1150

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1149

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1148

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1147

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1146

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1145

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.