← Home

@teambit/insights

51
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
npm-metadata no-description AI (npm-metadata): Established package with 2946 versions; missing description is stable metadata gap, not malware signal. ai
provenance no-provenance AI (provenance): Provenance absence is a best-practice gap, not a security blocker for established packages. ai
dependencies unvetted-dep:@teambit/issues AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai
dependencies unvetted-dep:@teambit/harmony AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai
dependencies unvetted-dep:@teambit/bit-error AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai
dependencies unvetted-dep:@teambit/cli AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai
dependencies unvetted-dep:@teambit/component-id AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai
dependencies unvetted-dep:@teambit/component-issues AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai
dependencies unvetted-dep:@teambit/component AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai
dependencies unvetted-dep:@teambit/graph AI (dependencies): Sibling @teambit/* monorepo dep; stable pattern across all teambit package versions. ai

Versions (showing 51 of 800)

View all versions
Version Deps Published
1.0.1078 12 / 4
1.0.1077 12 / 4
1.0.1076 12 / 4
1.0.1075 12 / 4
1.0.1074 12 / 4
1.0.1073 12 / 4
1.0.1072 12 / 4
1.0.1071 12 / 4
1.0.1070 12 / 4
1.0.1069 12 / 4
1.0.1068 12 / 4
1.0.1067 12 / 4
1.0.1066 12 / 4
1.0.1065 12 / 4
1.0.1064 12 / 4
1.0.1063 12 / 4
1.0.1062 12 / 4
1.0.1061 12 / 4
1.0.1060 12 / 4
1.0.1059 12 / 4
1.0.1058 12 / 4
1.0.1057 12 / 4
1.0.1056 12 / 4
1.0.1055 12 / 4
1.0.1054 12 / 4
1.0.1053 12 / 4
1.0.1052 12 / 4
1.0.1051 12 / 4
1.0.1050 12 / 4
1.0.1049 12 / 4
1.0.1048 12 / 4
1.0.1047 12 / 4
1.0.1046 12 / 4
1.0.1045 12 / 4
1.0.1044 12 / 4
1.0.1043 12 / 4
1.0.1042 12 / 4
1.0.1041 12 / 4
1.0.1040 12 / 4
1.0.1039 12 / 4
1.0.1038 12 / 4
1.0.1037 12 / 4
1.0.1036 12 / 4
1.0.1035 12 / 4
1.0.1034 12 / 4
1.0.1033 12 / 4
1.0.1032 12 / 4
1.0.1031 12 / 4
1.0.1030 12 / 4
1.0.1029 12 / 4
1.0.1028 12 / 4

v1.0.1078

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1 finding
INFO No provenance attestation provenance

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