@teambit/merge-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.utils | AI (dependencies): Internal same-org Bit monorepo dependency, not unvetted third-party code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @teambit package within same monorepo/org. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.feature-toggle | AI (dependencies): Same @teambit org scope; consistent with this package's established dependency pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.cli.prompts | AI (dependencies): Same @teambit org scope; consistent with this package's established dependency pattern. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI/CD releasing many packages rapidly; consistent pattern across 2437+ versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.bit-map | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/component.snap-distance | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.get-basic-log | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/component.modules.merge-helper | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/lane-id | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Same-org @teambit/* sibling package from the teambit/bit monorepo; stable pattern across versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Bit ecosystem packages routinely omit npm descriptions; not a malware indicator here. | ai | |
| phantom-deps | phantom-dep:@teambit/component.snap-distance | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for Bit's modular monorepo structure. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes thousands of packages without Sigstore provenance; consistent across the ecosystem. | ai |
Versions (showing 100 of 401)
| Version | Deps | Published |
|---|---|---|
| 1.0.231 | 22 / 5 | |
| 1.0.230 | 22 / 5 | |
| 1.0.229 | 22 / 5 | |
| 1.0.228 | 22 / 5 | |
| 1.0.227 | 22 / 5 | |
| 1.0.226 | 22 / 5 | |
| 1.0.225 | 22 / 5 | |
| 1.0.224 | 22 / 5 | |
| 1.0.223 | 22 / 5 | |
| 1.0.222 | 22 / 5 | |
| 1.0.221 | 22 / 5 | |
| 1.0.220 | 22 / 5 | |
| 1.0.219 | 22 / 5 | |
| 1.0.218 | 22 / 5 | |
| 1.0.217 | 22 / 5 | |
| 1.0.216 | 22 / 5 | |
| 1.0.215 | 22 / 5 | |
| 1.0.214 | 22 / 5 | |
| 1.0.213 | 22 / 5 | |
| 1.0.212 | 22 / 5 | |
| 1.0.211 | 22 / 5 | |
| 1.0.210 | 22 / 5 | |
| 1.0.209 | 22 / 5 | |
| 1.0.208 | 22 / 5 | |
| 1.0.207 | 22 / 5 | |
| 1.0.206 | 22 / 5 | |
| 1.0.205 | 22 / 5 | |
| 1.0.204 | 22 / 5 | |
| 1.0.203 | 22 / 5 | |
| 1.0.202 | 22 / 5 | |
| 1.0.201 | 22 / 5 | |
| 1.0.200 | 22 / 5 | |
| 1.0.199 | 22 / 5 | |
| 1.0.198 | 22 / 5 | |
| 1.0.197 | 22 / 5 | |
| 1.0.196 | 22 / 5 | |
| 1.0.195 | 22 / 5 | |
| 1.0.194 | 22 / 5 | |
| 1.0.193 | 22 / 5 | |
| 1.0.192 | 22 / 5 | |
| 1.0.191 | 22 / 5 | |
| 1.0.190 | 22 / 5 | |
| 1.0.189 | 22 / 5 | |
| 1.0.188 | 22 / 5 | |
| 1.0.187 | 22 / 5 | |
| 1.0.186 | 22 / 5 | |
| 1.0.185 | 22 / 5 | |
| 1.0.184 | 22 / 5 | |
| 1.0.183 | 22 / 5 | |
| 1.0.182 | 22 / 5 | |
| 1.0.181 | 22 / 5 | |
| 1.0.180 | 22 / 5 | |
| 1.0.179 | 22 / 5 | |
| 1.0.178 | 22 / 5 | |
| 1.0.177 | 22 / 5 | |
| 1.0.176 | 22 / 5 | |
| 1.0.175 | 22 / 5 | |
| 1.0.174 | 22 / 5 | |
| 1.0.173 | 22 / 5 | |
| 1.0.171 | 22 / 5 | |
| 1.0.170 | 22 / 5 | |
| 1.0.169 | 22 / 5 | |
| 1.0.168 | 22 / 5 | |
| 1.0.167 | 22 / 5 | |
| 1.0.166 | 22 / 5 | |
| 1.0.165 | 22 / 5 | |
| 1.0.164 | 22 / 5 | |
| 1.0.163 | 22 / 5 | |
| 1.0.162 | 22 / 5 | |
| 1.0.161 | 22 / 5 | |
| 1.0.160 | 22 / 5 | |
| 1.0.159 | 22 / 5 | |
| 1.0.158 | 22 / 5 | |
| 1.0.157 | 22 / 5 | |
| 1.0.156 | 22 / 5 | |
| 1.0.155 | 22 / 5 | |
| 1.0.154 | 22 / 5 | |
| 1.0.153 | 22 / 5 | |
| 1.0.152 | 22 / 5 | |
| 1.0.151 | 22 / 5 | |
| 1.0.150 | 22 / 5 | |
| 1.0.149 | 22 / 5 | |
| 1.0.148 | 22 / 5 | |
| 1.0.147 | 22 / 5 | |
| 1.0.146 | 22 / 5 | |
| 1.0.145 | 22 / 5 | |
| 1.0.144 | 22 / 5 | |
| 1.0.143 | 22 / 5 | |
| 1.0.142 | 22 / 6 | |
| 1.0.141 | 22 / 6 | |
| 1.0.140 | 22 / 6 | |
| 1.0.139 | 22 / 6 | |
| 1.0.138 | 22 / 6 | |
| 1.0.137 | 22 / 6 | |
| 1.0.136 | 22 / 6 | |
| 1.0.135 | 22 / 6 | |
| 1.0.134 | 22 / 6 | |
| 1.0.133 | 21 / 6 | |
| 1.0.132 | 21 / 6 | |
| 1.0.131 | 21 / 6 |
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.
v1.0.175
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.174
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.173
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.171
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.170
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.169
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.168
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.167
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.166
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.165
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.164
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.163
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.162
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.161
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.160
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.159
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.158
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.157
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.156
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.155
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.154
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.153
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.152
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.151
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.150
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.149
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.148
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.147
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.146
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.145
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.144
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.143
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.142
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.141
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.140
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.139
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.138
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.137
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.136
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.135
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.134
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.133
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.132
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.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.