@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 73 of 373)
| Version | Deps | Published |
|---|---|---|
| 1.0.73 | 47 / 12 | |
| 1.0.72 | 47 / 12 | |
| 1.0.71 | 47 / 12 | |
| 1.0.70 | 47 / 12 | |
| 1.0.69 | 47 / 12 | |
| 1.0.68 | 47 / 12 | |
| 1.0.67 | 47 / 12 | |
| 1.0.66 | 47 / 12 | |
| 1.0.65 | 47 / 12 | |
| 1.0.64 | 47 / 12 | |
| 1.0.63 | 47 / 12 | |
| 1.0.62 | 47 / 12 | |
| 1.0.61 | 47 / 12 | |
| 1.0.60 | 47 / 12 | |
| 1.0.59 | 46 / 12 | |
| 1.0.58 | 46 / 12 | |
| 1.0.57 | 46 / 12 | |
| 1.0.56 | 46 / 12 | |
| 1.0.55 | 46 / 12 | |
| 1.0.54 | 46 / 12 | |
| 1.0.53 | 46 / 12 | |
| 1.0.52 | 46 / 12 | |
| 1.0.51 | 46 / 12 | |
| 1.0.50 | 46 / 12 | |
| 1.0.49 | 46 / 12 | |
| 1.0.48 | 46 / 12 | |
| 1.0.47 | 46 / 12 | |
| 1.0.46 | 46 / 12 | |
| 1.0.45 | 46 / 12 | |
| 1.0.44 | 46 / 12 | |
| 1.0.43 | 46 / 12 | |
| 1.0.42 | 46 / 12 | |
| 1.0.41 | 46 / 12 | |
| 1.0.40 | 46 / 12 | |
| 1.0.39 | 46 / 12 | |
| 1.0.38 | 46 / 12 | |
| 1.0.37 | 46 / 12 | |
| 1.0.36 | 46 / 12 | |
| 1.0.35 | 46 / 12 | |
| 1.0.34 | 46 / 12 | |
| 1.0.33 | 46 / 12 | |
| 1.0.32 | 46 / 12 | |
| 1.0.31 | 46 / 12 | |
| 1.0.30 | 46 / 12 | |
| 1.0.28 | 46 / 12 | |
| 1.0.27 | 45 / 12 | |
| 1.0.26 | 45 / 12 | |
| 1.0.25 | 45 / 12 | |
| 1.0.24 | 45 / 12 | |
| 1.0.23 | 45 / 12 | |
| 1.0.22 | 45 / 12 | |
| 1.0.21 | 45 / 12 | |
| 1.0.20 | 45 / 12 | |
| 1.0.19 | 45 / 12 | |
| 1.0.18 | 45 / 12 | |
| 1.0.17 | 45 / 12 | |
| 1.0.16 | 45 / 12 | |
| 1.0.15 | 45 / 12 | |
| 1.0.14 | 45 / 12 | |
| 1.0.13 | 45 / 12 | |
| 1.0.12 | 45 / 12 | |
| 1.0.11 | 45 / 12 | |
| 1.0.10 | 45 / 12 | |
| 1.0.9 | 45 / 12 | |
| 1.0.8 | 45 / 12 | |
| 1.0.7 | 45 / 12 | |
| 1.0.6 | 45 / 12 | |
| 1.0.5 | 45 / 12 | |
| 1.0.4 | 45 / 12 | |
| 1.0.3 | 45 / 12 | |
| 1.0.2 | 45 / 12 | |
| 1.0.1 | 45 / 12 | |
| 1.0.0 | 45 / 12 |
v1.0.73
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.72
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.71
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.70
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.69
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.68
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.67
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.66
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.65
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.64
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.63
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.62
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.61
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.60
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.59
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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.51
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.50
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.49
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.48
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.47
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.46
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.45
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.44
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.43
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.42
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.41
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.40
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.39
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.38
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.37
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.36
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.35
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.34
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.33
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.32
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.31
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.30
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.28
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.27
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.26
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.25
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.24
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.23
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.22
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.21
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.20
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.19
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.18
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.17
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.16
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.15
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.14
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.13
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.12
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.11
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.10
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.9
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.8
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.7
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.6
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.5
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.4
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.3
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.2
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.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.