← Home

@teambit/dev-files

npm Repository Homepage
100
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

teambit-ownershohamgiladdavidfirstranm8guysaaritaymendelerezbitjoshk2redigmayona007

Keywords

bitbit-aspectbit-core-aspectcomponentscollaborationweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Known maintainer manual publish per provenance record; not a takeover. ai
publish-pattern new-deps-added AI (publish-pattern): Same-org internal dependency addition, typical for this monorepo's release pattern. ai
publish-pattern rapid-publish AI (publish-pattern): teambit uses automated CI releases; rapid successive publishes are normal for this org across 3200+ versions. ai
dependencies unvetted-dep:@teambit/graphql AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
dependencies unvetted-dep:@teambit/harmony AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
dependencies unvetted-dep:@teambit/component AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
dependencies unvetted-dep:@teambit/workspace AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
dependencies unvetted-dep:@teambit/cli AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
dependencies unvetted-dep:@teambit/legacy.consumer-component AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
phantom-deps phantom-dep:@teambit/component.sources AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive in Bit's component-based architecture. ai
provenance no-provenance AI (provenance): Established Bit monorepo package; lack of provenance is consistent across all 2825 versions. ai
npm-metadata no-description AI (npm-metadata): Bit core aspects consistently omit npm descriptions; homepage and componentId fields provide context. ai
dependencies unvetted-dep:@teambit/component.sources AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
dependencies unvetted-dep:@teambit/envs AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai
dependencies unvetted-dep:@teambit/scope AI (dependencies): Sibling @teambit/* dep from the same Bit monorepo; structurally unvetted but not a security risk. ai

Versions (showing 100 of 222)

Version Deps Published
1.0.1060 11 / 4
1.0.1056 11 / 4
1.0.1055 11 / 4
1.0.1054 11 / 4
1.0.1052 11 / 4
1.0.1051 11 / 4
1.0.1021 11 / 4
1.0.996 11 / 4
1.0.981 11 / 4
1.0.978 11 / 4
1.0.976 11 / 4
1.0.972 11 / 4
1.0.971 11 / 4
1.0.970 11 / 4
1.0.969 11 / 4
1.0.968 11 / 4
1.0.966 11 / 4
1.0.963 11 / 4
1.0.957 11 / 4
1.0.956 11 / 4
1.0.955 11 / 4
1.0.951 11 / 4
1.0.950 11 / 4
1.0.946 11 / 4
1.0.945 11 / 4
1.0.944 11 / 4
1.0.943 11 / 4
1.0.942 11 / 4
1.0.941 11 / 4
1.0.940 11 / 4
1.0.939 11 / 4
1.0.938 11 / 4
1.0.937 11 / 4
1.0.936 11 / 4
1.0.935 11 / 4
1.0.933 11 / 4
1.0.932 11 / 4
1.0.931 11 / 4
1.0.930 11 / 4
1.0.929 11 / 4
1.0.928 11 / 4
1.0.927 11 / 4
1.0.926 11 / 4
1.0.925 11 / 4
1.0.911 11 / 4
1.0.898 11 / 4
1.0.821 11 / 4
1.0.573 11 / 4
1.0.553 11 / 4
1.0.552 11 / 4
1.0.551 11 / 4
1.0.542 11 / 4
1.0.533 11 / 4
1.0.532 11 / 4
1.0.530 11 / 4
1.0.527 11 / 4
1.0.526 11 / 4
1.0.523 11 / 4
1.0.521 11 / 4
1.0.520 11 / 4
1.0.518 11 / 4
1.0.515 11 / 4
1.0.514 11 / 4
1.0.512 11 / 5
1.0.510 11 / 5
1.0.506 11 / 5
1.0.492 11 / 5
1.0.488 11 / 5
1.0.486 10 / 5
1.0.484 10 / 5
1.0.482 10 / 5
1.0.480 10 / 5
1.0.479 10 / 5
1.0.476 10 / 5
1.0.474 10 / 5
1.0.473 10 / 5
1.0.470 10 / 5
1.0.468 10 / 5
1.0.466 10 / 5
1.0.464 10 / 5
1.0.462 10 / 5
1.0.461 10 / 5
1.0.460 10 / 5
1.0.458 10 / 5
1.0.456 10 / 5
1.0.454 10 / 5
1.0.451 10 / 5
1.0.448 10 / 5
1.0.446 10 / 5
1.0.444 10 / 5
1.0.442 10 / 5
1.0.440 10 / 5
1.0.438 10 / 5
1.0.436 10 / 5
1.0.432 10 / 5
1.0.431 10 / 5
1.0.430 10 / 5
1.0.429 10 / 5
1.0.427 10 / 5
1.0.425 10 / 5
Showing 100 of 222 Next page →

v1.0.1060

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1056

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1055

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1054

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1052

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1051

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.981

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.978

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.976

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.821

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidfirst → teambit-owner (on 2025-11-25, known maintainer) provenance

This version was published by a different npm account (teambit-owner) than the most recent previously approved version (davidfirst) on 2025-11-25, 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.573

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.553

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.552

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.551

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.542

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.533

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.532

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.530

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.527

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.526

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.523

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.521

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.520

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.518

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.515

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.514

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.512

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.510

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.506

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.492

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.488

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: davidfirst → shohamgilad (on 2024-12-10, known maintainer) provenance

This version was published by a different npm account (shohamgilad) than the most recent previously approved version (davidfirst) on 2024-12-10, but shohamgilad 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.486

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.484

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.482

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.480

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.479

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.476

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.474

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.473

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.470

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.468

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.466

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.464

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.462

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.461

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.460

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.458

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.456

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.454

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.451

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.448

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.446

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.444

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.442

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.440

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.438

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.436

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.432

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.431

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.430

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.429

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.427

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.425

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.