@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.175 | 44 / 11 | |
| 1.0.174 | 44 / 11 | |
| 1.0.173 | 44 / 11 | |
| 1.0.171 | 44 / 11 | |
| 1.0.170 | 44 / 11 | |
| 1.0.169 | 44 / 11 | |
| 1.0.168 | 44 / 11 | |
| 1.0.167 | 44 / 11 | |
| 1.0.166 | 44 / 11 | |
| 1.0.165 | 44 / 11 | |
| 1.0.164 | 44 / 11 | |
| 1.0.163 | 44 / 11 | |
| 1.0.162 | 44 / 11 | |
| 1.0.161 | 44 / 11 | |
| 1.0.160 | 44 / 11 | |
| 1.0.159 | 44 / 11 | |
| 1.0.158 | 44 / 11 | |
| 1.0.157 | 44 / 11 | |
| 1.0.156 | 44 / 11 | |
| 1.0.155 | 44 / 11 | |
| 1.0.154 | 44 / 11 | |
| 1.0.153 | 44 / 11 | |
| 1.0.152 | 44 / 11 | |
| 1.0.151 | 44 / 11 | |
| 1.0.150 | 44 / 11 | |
| 1.0.149 | 44 / 11 | |
| 1.0.148 | 44 / 9 | |
| 1.0.147 | 44 / 9 | |
| 1.0.146 | 44 / 9 | |
| 1.0.145 | 44 / 9 | |
| 1.0.144 | 44 / 9 | |
| 1.0.143 | 44 / 9 | |
| 1.0.142 | 44 / 9 | |
| 1.0.141 | 44 / 9 | |
| 1.0.140 | 44 / 9 | |
| 1.0.139 | 44 / 9 | |
| 1.0.138 | 44 / 9 | |
| 1.0.137 | 44 / 9 | |
| 1.0.136 | 44 / 9 | |
| 1.0.135 | 44 / 9 | |
| 1.0.134 | 44 / 9 | |
| 1.0.133 | 44 / 9 | |
| 1.0.132 | 44 / 9 | |
| 1.0.131 | 44 / 9 | |
| 1.0.130 | 44 / 9 | |
| 1.0.129 | 44 / 9 | |
| 1.0.128 | 45 / 8 | |
| 1.0.127 | 45 / 8 | |
| 1.0.126 | 45 / 8 | |
| 1.0.125 | 45 / 8 | |
| 1.0.124 | 45 / 8 | |
| 1.0.123 | 45 / 8 | |
| 1.0.122 | 45 / 8 | |
| 1.0.121 | 45 / 8 | |
| 1.0.120 | 45 / 8 | |
| 1.0.119 | 45 / 8 | |
| 1.0.117 | 45 / 8 | |
| 1.0.116 | 45 / 8 | |
| 1.0.115 | 45 / 8 | |
| 1.0.114 | 45 / 8 | |
| 1.0.113 | 45 / 8 | |
| 1.0.112 | 45 / 8 | |
| 1.0.111 | 45 / 8 | |
| 1.0.110 | 45 / 8 | |
| 1.0.109 | 45 / 8 | |
| 1.0.108 | 45 / 8 | |
| 1.0.107 | 47 / 12 | |
| 1.0.106 | 47 / 12 | |
| 1.0.105 | 47 / 12 | |
| 1.0.104 | 47 / 12 | |
| 1.0.103 | 47 / 12 | |
| 1.0.102 | 47 / 12 | |
| 1.0.101 | 47 / 12 | |
| 1.0.100 | 47 / 12 | |
| 1.0.99 | 47 / 12 | |
| 1.0.98 | 47 / 12 | |
| 1.0.97 | 47 / 12 | |
| 1.0.96 | 47 / 12 | |
| 1.0.95 | 47 / 12 | |
| 1.0.94 | 47 / 12 | |
| 1.0.93 | 47 / 12 | |
| 1.0.92 | 47 / 12 | |
| 1.0.91 | 47 / 12 | |
| 1.0.90 | 47 / 12 | |
| 1.0.89 | 47 / 12 | |
| 1.0.88 | 47 / 12 | |
| 1.0.87 | 47 / 12 | |
| 1.0.86 | 47 / 12 | |
| 1.0.85 | 47 / 12 | |
| 1.0.84 | 47 / 12 | |
| 1.0.83 | 47 / 12 | |
| 1.0.82 | 47 / 12 | |
| 1.0.81 | 47 / 12 | |
| 1.0.80 | 47 / 12 | |
| 1.0.79 | 47 / 12 | |
| 1.0.78 | 47 / 12 | |
| 1.0.77 | 47 / 12 | |
| 1.0.76 | 47 / 12 | |
| 1.0.75 | 47 / 12 | |
| 1.0.74 | 47 / 12 |
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.
v1.0.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.127
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.109
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.108
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.107
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.