← Home

@teambit/schema

12
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

teambit-ownershohamgiladdavidfirstranm8guysaaritaymendelerezbitjoshk2redigmayona007

Keywords

bitbit-aspectbit-core-aspectcomponentscollaborationweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Both new deps are well-known or same-org packages; no malicious signal. ai
dependencies unvetted-dep:@teambit/envs AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/scope AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/logger AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/builder AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/graphql AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/harmony AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/component AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/formatter AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/workspace AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/cli AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/scope.network AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/legacy.constants AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/defender.prettier.config-mutator AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/semantics.entities.semantic-schema AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
dependencies unvetted-dep:@teambit/semantics.entities.semantic-schema-diff AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai
phantom-deps phantom-dep:@teambit/defender.prettier.config-mutator AI (phantom-deps): Same-org sibling dep in a monorepo; phantom-dep heuristic is unreliable here. ai
npm-metadata no-description AI (npm-metadata): Bit monorepo components consistently omit npm description; not a malware signal. ai
provenance no-provenance AI (provenance): Established package predating widespread provenance adoption; no provenance across all teambit/* packages. ai
dependencies unvetted-dep:@teambit/typescript AI (dependencies): Sibling @teambit monorepo dep; structural false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
1.0.996 21 / 8
1.0.972 21 / 8
1.0.971 21 / 8
1.0.970 21 / 8
1.0.968 21 / 8
1.0.928 21 / 8
1.0.925 19 / 8
1.0.619 19 / 8
1.0.613 18 / 8
1.0.612 18 / 8
1.0.611 18 / 8
1.0.610 18 / 8

v1.0.996

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.972

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.971

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.970

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.928

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.619

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.613

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.612

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.611

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.610

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.