@teambit/watcher
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): teambit uses automated CI releases across many packages simultaneously; rapid publish is expected for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Established teambit org package with 2050 versions; maintainer removal is routine org hygiene, not a takeover signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with 2007 versions; missing description is stable pattern, not malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is cosmetic for established package; not a security blocker. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/workspace | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/ipc-events | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/config-store | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/cli | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.logger | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.bit-map | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.send-server-sent-events | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@teambit/legacy.bit-map | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages with indirect usage. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/scope | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/logger | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/pubsub | AI (dependencies): Same-org sibling dep from teambit/bit monorepo; expected pattern across all versions. | ai |
Versions (showing 72 of 272)
| Version | Deps | Published |
|---|---|---|
| 1.0.328 | 17 / 5 | |
| 1.0.327 | 17 / 5 | |
| 1.0.326 | 17 / 5 | |
| 1.0.325 | 17 / 5 | |
| 1.0.324 | 17 / 5 | |
| 1.0.323 | 17 / 5 | |
| 1.0.322 | 17 / 5 | |
| 1.0.321 | 17 / 5 | |
| 1.0.320 | 17 / 5 | |
| 1.0.319 | 17 / 5 | |
| 1.0.318 | 17 / 5 | |
| 1.0.317 | 17 / 5 | |
| 1.0.316 | 17 / 5 | |
| 1.0.315 | 17 / 5 | |
| 1.0.314 | 17 / 5 | |
| 1.0.313 | 17 / 5 | |
| 1.0.312 | 17 / 5 | |
| 1.0.311 | 17 / 5 | |
| 1.0.310 | 17 / 5 | |
| 1.0.309 | 17 / 5 | |
| 1.0.308 | 17 / 5 | |
| 1.0.307 | 17 / 5 | |
| 1.0.306 | 17 / 5 | |
| 1.0.305 | 17 / 5 | |
| 1.0.304 | 17 / 5 | |
| 1.0.303 | 17 / 5 | |
| 1.0.302 | 17 / 5 | |
| 1.0.301 | 17 / 5 | |
| 1.0.300 | 17 / 5 | |
| 1.0.299 | 17 / 5 | |
| 1.0.298 | 17 / 5 | |
| 1.0.297 | 17 / 5 | |
| 1.0.296 | 17 / 5 | |
| 1.0.295 | 17 / 5 | |
| 1.0.294 | 17 / 5 | |
| 1.0.293 | 17 / 5 | |
| 1.0.292 | 17 / 5 | |
| 1.0.291 | 17 / 5 | |
| 1.0.290 | 17 / 5 | |
| 1.0.289 | 17 / 5 | |
| 1.0.288 | 17 / 5 | |
| 1.0.287 | 17 / 5 | |
| 1.0.286 | 17 / 5 | |
| 1.0.285 | 17 / 5 | |
| 1.0.284 | 17 / 5 | |
| 1.0.283 | 17 / 5 | |
| 1.0.282 | 17 / 5 | |
| 1.0.281 | 17 / 5 | |
| 1.0.280 | 17 / 5 | |
| 1.0.279 | 17 / 5 | |
| 1.0.278 | 17 / 5 | |
| 1.0.277 | 17 / 5 | |
| 1.0.276 | 17 / 5 | |
| 1.0.275 | 17 / 5 | |
| 1.0.274 | 17 / 5 | |
| 1.0.273 | 17 / 5 | |
| 1.0.272 | 17 / 5 | |
| 1.0.271 | 17 / 5 | |
| 1.0.270 | 17 / 5 | |
| 1.0.269 | 17 / 5 | |
| 1.0.268 | 17 / 5 | |
| 1.0.267 | 17 / 5 | |
| 1.0.266 | 17 / 5 | |
| 1.0.265 | 17 / 5 | |
| 1.0.264 | 17 / 5 | |
| 1.0.263 | 17 / 5 | |
| 1.0.262 | 17 / 5 | |
| 1.0.261 | 17 / 5 | |
| 1.0.260 | 17 / 5 | |
| 1.0.259 | 17 / 5 | |
| 1.0.258 | 17 / 5 | |
| 1.0.257 | 17 / 5 |
v1.0.328
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.327
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.326
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.325
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.324
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.323
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.319
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.318
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.317
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.316
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.315
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.314
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.313
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.312
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.311
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.310
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.309
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.308
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.307
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.306
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.305
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.304
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.303
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.302
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.301
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.300
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.299
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.298
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.297
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.296
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.295
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.294
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.293
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.292
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.291
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.290
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.289
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.288
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.287
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.286
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.285
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.284
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.283
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.282
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.281
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.280
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.279
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.278
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.