@teambit/lanes
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/legacy.cli.prompts | AI (dependencies): Internal @teambit ecosystem dependency; consistent with this package's established dependency pattern. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit publishes many packages simultaneously via automated CI; rapid publish is a stable pattern for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable false positive; teambit core aspect packages consistently omit descriptions across all versions. | ai | |
| provenance | no-provenance | AI (provenance): teambit publishes without Sigstore provenance; consistent across all 2778 versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/scope.ui.scope-icon | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.component-diff | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.component-list | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.ui.lane-overview | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component.snap-distance | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.entities.lane-diff | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.modules.create-lane | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.concurrency | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.ui.compare.lane-compare | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.ui.menus.use-lanes-menu | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component.modules.merge-helper | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.ui.navigation.lane-switcher | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.ui.compare.lane-compare-page | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/lanes.ui.menus.lanes-overview-menu | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/git.modules.git-executable | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/scope.network | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/scope.remotes | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Internal @teambit monorepo sub-package; stable pattern across all versions. | ai |
Versions (showing 100 of 373)
| Version | Deps | Published |
|---|---|---|
| 1.0.277 | 45 / 11 | |
| 1.0.276 | 45 / 11 | |
| 1.0.275 | 45 / 11 | |
| 1.0.274 | 45 / 11 | |
| 1.0.273 | 45 / 11 | |
| 1.0.272 | 45 / 11 | |
| 1.0.271 | 45 / 11 | |
| 1.0.270 | 45 / 11 | |
| 1.0.269 | 45 / 11 | |
| 1.0.268 | 45 / 11 | |
| 1.0.267 | 45 / 11 | |
| 1.0.266 | 45 / 11 | |
| 1.0.265 | 45 / 11 | |
| 1.0.264 | 45 / 11 | |
| 1.0.263 | 45 / 11 | |
| 1.0.262 | 45 / 11 | |
| 1.0.261 | 45 / 11 | |
| 1.0.260 | 45 / 11 | |
| 1.0.259 | 45 / 11 | |
| 1.0.258 | 45 / 11 | |
| 1.0.257 | 45 / 11 | |
| 1.0.256 | 45 / 11 | |
| 1.0.255 | 45 / 11 | |
| 1.0.254 | 45 / 11 | |
| 1.0.253 | 45 / 11 | |
| 1.0.252 | 45 / 11 | |
| 1.0.251 | 45 / 11 | |
| 1.0.250 | 45 / 11 | |
| 1.0.249 | 44 / 11 | |
| 1.0.248 | 44 / 11 | |
| 1.0.247 | 44 / 11 | |
| 1.0.246 | 44 / 11 | |
| 1.0.245 | 44 / 11 | |
| 1.0.244 | 44 / 11 | |
| 1.0.243 | 44 / 11 | |
| 1.0.242 | 44 / 11 | |
| 1.0.241 | 44 / 11 | |
| 1.0.240 | 44 / 11 | |
| 1.0.239 | 44 / 11 | |
| 1.0.238 | 44 / 11 | |
| 1.0.237 | 44 / 11 | |
| 1.0.235 | 44 / 11 | |
| 1.0.234 | 44 / 11 | |
| 1.0.233 | 44 / 11 | |
| 1.0.231 | 44 / 11 | |
| 1.0.230 | 44 / 11 | |
| 1.0.229 | 44 / 11 | |
| 1.0.228 | 44 / 11 | |
| 1.0.227 | 44 / 11 | |
| 1.0.226 | 44 / 11 | |
| 1.0.225 | 44 / 11 | |
| 1.0.224 | 44 / 11 | |
| 1.0.223 | 44 / 11 | |
| 1.0.222 | 44 / 11 | |
| 1.0.221 | 44 / 11 | |
| 1.0.220 | 44 / 11 | |
| 1.0.219 | 44 / 11 | |
| 1.0.218 | 44 / 11 | |
| 1.0.217 | 44 / 11 | |
| 1.0.216 | 44 / 11 | |
| 1.0.215 | 44 / 11 | |
| 1.0.214 | 44 / 11 | |
| 1.0.213 | 44 / 11 | |
| 1.0.212 | 44 / 11 | |
| 1.0.211 | 44 / 11 | |
| 1.0.210 | 44 / 11 | |
| 1.0.209 | 44 / 11 | |
| 1.0.208 | 44 / 11 | |
| 1.0.207 | 44 / 11 | |
| 1.0.206 | 44 / 11 | |
| 1.0.205 | 44 / 11 | |
| 1.0.204 | 44 / 11 | |
| 1.0.203 | 44 / 11 | |
| 1.0.202 | 44 / 11 | |
| 1.0.201 | 44 / 11 | |
| 1.0.200 | 44 / 11 | |
| 1.0.199 | 44 / 11 | |
| 1.0.198 | 44 / 11 | |
| 1.0.197 | 44 / 11 | |
| 1.0.196 | 44 / 11 | |
| 1.0.195 | 44 / 11 | |
| 1.0.194 | 44 / 11 | |
| 1.0.193 | 44 / 11 | |
| 1.0.192 | 44 / 11 | |
| 1.0.191 | 44 / 11 | |
| 1.0.190 | 44 / 11 | |
| 1.0.189 | 44 / 11 | |
| 1.0.188 | 44 / 11 | |
| 1.0.187 | 44 / 11 | |
| 1.0.186 | 44 / 11 | |
| 1.0.185 | 44 / 11 | |
| 1.0.184 | 44 / 11 | |
| 1.0.183 | 44 / 11 | |
| 1.0.182 | 44 / 11 | |
| 1.0.181 | 44 / 11 | |
| 1.0.180 | 44 / 11 | |
| 1.0.179 | 44 / 11 | |
| 1.0.178 | 44 / 11 | |
| 1.0.177 | 44 / 11 | |
| 1.0.176 | 44 / 11 |
v1.0.277
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.276
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.275
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.274
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.273
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.272
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.271
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.270
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.269
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.268
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.267
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.266
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.265
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.264
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.263
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.262
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.261
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.260
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.259
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.258
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.257
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.256
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.255
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.254
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.253
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.252
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.251
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.250
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.249
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.248
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.247
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.246
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.245
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.244
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.243
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.242
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.241
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.240
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.239
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.238
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.237
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.235
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.234
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.233
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.231
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.230
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.229
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.228
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.227
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.226
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.225
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.224
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.223
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.222
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.221
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.220
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.219
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.218
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.217
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.216
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.215
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.214
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.213
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.212
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.211
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.210
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.209
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.208
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.207
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.206
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.205
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.204
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.203
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.202
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.201
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.200
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.199
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.198
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.197
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.196
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.195
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.194
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.193
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.192
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.191
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.190
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.189
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.188
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.187
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.186
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.185
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.184
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.183
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.182
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.181
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.180
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.179
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.178
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.177
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.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.