@teambit/pkg
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 | new-deps-added | AI (publish-pattern): First-party @teambit monorepo dependency, not a supply-chain risk. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): teambit publishes many coordinated monorepo packages simultaneously; rapid publish is a stable pattern for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is stable pattern for internal teambit packages. | ai | |
| provenance | no-provenance | AI (provenance): Provenance not enabled; stable across 2945 versions of this established package. | ai | |
| dependencies | unvetted-dep:is-relative-path | AI (dependencies): Well-known utility package; no malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.scope | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.utils | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/component-issues | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/component-version | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/component.sources | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.extension-data | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@pnpm/plugin-commands-publishing | AI (dependencies): Official pnpm plugin; no malware signal. | ai | |
| dependencies | unvetted-dep:@teambit/component-package-version | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer-component | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/ui-foundation.ui.use-box.menu | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| dependencies | unvetted-dep:@teambit/harmony.modules.in-memory-cache | AI (dependencies): Internal @teambit monorepo dependency. | ai | |
| phantom-deps | phantom-dep:@teambit/compiler | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal @teambit monorepo dependency; stable pattern across all versions. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @teambit/pkg is a legitimate Bit core aspect, not a typosquat of 'pg'; scoped package in an established monorepo. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 1.0.1064 | 39 / 7 | |
| 1.0.1056 | 39 / 7 | |
| 1.0.1054 | 39 / 7 | |
| 1.0.1052 | 39 / 7 | |
| 1.0.1021 | 39 / 7 | |
| 1.0.999 | 39 / 7 | |
| 1.0.990 | 39 / 7 | |
| 1.0.981 | 39 / 7 | |
| 1.0.980 | 39 / 7 | |
| 1.0.979 | 39 / 7 | |
| 1.0.977 | 39 / 7 | |
| 1.0.972 | 39 / 7 | |
| 1.0.971 | 39 / 7 | |
| 1.0.970 | 39 / 7 | |
| 1.0.968 | 39 / 7 | |
| 1.0.838 | 39 / 7 | |
| 1.0.437 | 37 / 7 | |
| 1.0.322 | 35 / 8 | |
| 1.0.321 | 34 / 8 | |
| 1.0.320 | 34 / 8 | |
| 1.0.319 | 34 / 8 | |
| 1.0.318 | 34 / 8 | |
| 1.0.317 | 34 / 8 | |
| 1.0.316 | 34 / 8 | |
| 1.0.315 | 34 / 8 | |
| 1.0.314 | 34 / 8 | |
| 1.0.313 | 34 / 8 | |
| 1.0.312 | 34 / 8 | |
| 1.0.311 | 34 / 8 | |
| 1.0.310 | 34 / 8 | |
| 1.0.309 | 34 / 8 | |
| 1.0.308 | 34 / 8 | |
| 1.0.307 | 34 / 8 | |
| 1.0.306 | 34 / 8 | |
| 1.0.305 | 34 / 8 | |
| 1.0.304 | 34 / 8 | |
| 1.0.303 | 34 / 8 | |
| 1.0.302 | 34 / 8 | |
| 1.0.301 | 34 / 8 | |
| 1.0.300 | 34 / 8 | |
| 1.0.299 | 34 / 8 | |
| 1.0.298 | 34 / 8 | |
| 1.0.297 | 34 / 8 | |
| 1.0.296 | 34 / 8 | |
| 1.0.295 | 34 / 8 | |
| 1.0.294 | 34 / 8 | |
| 1.0.293 | 34 / 8 | |
| 1.0.292 | 34 / 8 | |
| 1.0.291 | 34 / 8 | |
| 1.0.290 | 34 / 8 | |
| 1.0.289 | 34 / 8 |
v1.0.1064
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1056
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1054
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.437
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.322
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.321
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.320
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.319
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.