@teambit/importer
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine monorepo maintainer list churn, publisher confirmed as known teambit maintainer. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @teambit dep added in lockstep monorepo release; not a supply-chain risk. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit publishes many packages simultaneously via automated monorepo CI; rapid publish is a stable false positive for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component; description often omitted in internal packages. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is ~12% across npm; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy-bit-id | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/scope.remotes | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.analytics | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope-api | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/component.sources | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/toolbox.promise.map-pool | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer-component | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.concurrency | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/component.modules.merge-helper | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/pkg.modules.component-package-name | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/component-version | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/lane-id | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope | AI (dependencies): Internal @teambit monorepo sibling; stable false positive for this package family. | ai |
Versions (showing 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 1.0.1065 | 35 / 3 | |
| 1.0.1060 | 35 / 3 | |
| 1.0.1052 | 35 / 3 | |
| 1.0.1051 | 35 / 3 | |
| 1.0.1021 | 35 / 3 | |
| 1.0.999 | 35 / 3 | |
| 1.0.989 | 35 / 3 | |
| 1.0.988 | 35 / 3 | |
| 1.0.972 | 35 / 3 | |
| 1.0.971 | 35 / 3 | |
| 1.0.970 | 35 / 3 | |
| 1.0.968 | 35 / 3 | |
| 1.0.967 | 35 / 3 | |
| 1.0.966 | 35 / 3 | |
| 1.0.965 | 35 / 3 | |
| 1.0.959 | 35 / 3 | |
| 1.0.953 | 34 / 3 | |
| 1.0.949 | 34 / 3 | |
| 1.0.947 | 34 / 3 | |
| 1.0.942 | 34 / 3 | |
| 1.0.939 | 34 / 3 | |
| 1.0.934 | 34 / 3 | |
| 1.0.933 | 34 / 3 | |
| 1.0.931 | 34 / 3 | |
| 1.0.929 | 34 / 3 | |
| 1.0.928 | 34 / 3 | |
| 1.0.927 | 34 / 3 | |
| 1.0.926 | 34 / 3 | |
| 1.0.925 | 34 / 3 | |
| 1.0.886 | 34 / 3 | |
| 1.0.840 | 34 / 3 | |
| 1.0.720 | 34 / 3 | |
| 1.0.438 | 29 / 3 | |
| 1.0.410 | 29 / 4 | |
| 1.0.349 | 29 / 4 | |
| 1.0.344 | 29 / 4 | |
| 1.0.336 | 29 / 4 | |
| 1.0.334 | 29 / 4 | |
| 1.0.318 | 24 / 4 | |
| 1.0.317 | 23 / 4 | |
| 1.0.316 | 23 / 4 | |
| 1.0.315 | 23 / 4 | |
| 1.0.314 | 23 / 4 | |
| 1.0.313 | 23 / 4 | |
| 1.0.312 | 23 / 4 | |
| 1.0.311 | 23 / 4 | |
| 1.0.310 | 23 / 4 | |
| 1.0.309 | 23 / 4 | |
| 1.0.308 | 23 / 4 | |
| 1.0.307 | 23 / 4 | |
| 1.0.306 | 23 / 4 | |
| 1.0.305 | 23 / 4 | |
| 1.0.304 | 23 / 4 | |
| 1.0.303 | 23 / 4 | |
| 1.0.302 | 23 / 4 | |
| 1.0.301 | 23 / 4 | |
| 1.0.300 | 23 / 4 | |
| 1.0.299 | 23 / 4 | |
| 1.0.298 | 23 / 4 | |
| 1.0.297 | 23 / 4 | |
| 1.0.296 | 23 / 4 | |
| 1.0.295 | 23 / 4 | |
| 1.0.294 | 23 / 4 | |
| 1.0.293 | 23 / 4 | |
| 1.0.292 | 23 / 4 | |
| 1.0.291 | 23 / 4 | |
| 1.0.290 | 23 / 4 | |
| 1.0.289 | 23 / 4 | |
| 1.0.288 | 23 / 4 | |
| 1.0.287 | 23 / 4 | |
| 1.0.286 | 23 / 4 | |
| 1.0.285 | 23 / 4 | |
| 1.0.284 | 23 / 4 | |
| 1.0.283 | 23 / 4 | |
| 1.0.282 | 23 / 4 | |
| 1.0.281 | 23 / 4 | |
| 1.0.280 | 23 / 4 | |
| 1.0.279 | 23 / 4 | |
| 1.0.278 | 23 / 4 | |
| 1.0.277 | 23 / 4 | |
| 1.0.276 | 23 / 4 | |
| 1.0.275 | 23 / 4 | |
| 1.0.274 | 23 / 4 | |
| 1.0.273 | 23 / 4 | |
| 1.0.272 | 23 / 4 | |
| 1.0.271 | 23 / 4 | |
| 1.0.270 | 23 / 4 | |
| 1.0.269 | 23 / 4 | |
| 1.0.268 | 23 / 4 | |
| 1.0.267 | 23 / 4 | |
| 1.0.266 | 23 / 4 | |
| 1.0.265 | 23 / 4 | |
| 1.0.264 | 23 / 4 | |
| 1.0.263 | 23 / 4 | |
| 1.0.262 | 23 / 4 | |
| 1.0.261 | 23 / 4 | |
| 1.0.260 | 23 / 4 | |
| 1.0.259 | 23 / 4 | |
| 1.0.258 | 23 / 4 | |
| 1.0.257 | 23 / 4 |
v1.0.1065
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.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.840
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (teambit-owner) than the most recent previously approved version (davidfirst) on 2025-12-08, but teambit-owner is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.438
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.410
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.349
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.344
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.336
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.334
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.315
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.312
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.310
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.309
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.307
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.306
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.305
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.304
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.303
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.302
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.301
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.300
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.299
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.298
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.297
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.296
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.295
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.294
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.293
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.292
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.277
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.276
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.275
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.274
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.273
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.272
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.271
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.270
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.269
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.268
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.260
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-02, but davidfirst is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.259
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davidfirst) than the most recent previously approved version (shohamgilad) on 2024-05-01, but davidfirst is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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.