@teambit/compositions.ui.composition-compare Apache-2.0 21 versions

@teambit/compositions.ui.composition-compare

npm Repository Homepage

21

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

bitcomponentscollaborationwebreactreact-componentsangularangular-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:core-js	AI (phantom-deps): core-js is a known implicit polyfill dependency; stable false positive for this package.	ai	2026/05/17
phantom-deps	phantom-dep:@teambit/ui-foundation.ui.constants.z-indexes	AI (phantom-deps): Same-org @teambit scope dependency; phantom-dep heuristic unreliable for Bit component packages.	ai	2026/05/17
npm-metadata	no-description	AI (npm-metadata): Established teambit component package; missing description is a consistent pattern across their component library, not a malware signal.	ai	2026/05/17

Versions (showing 21 of 121)

Version	Deps	Published
0.0.161	11 / 7	2023-04-06
0.0.160	11 / 7	2023-03-29
0.0.159	11 / 7	2023-03-28
0.0.158	11 / 7	2023-03-27
0.0.157	11 / 7	2023-03-23
0.0.156	11 / 7	2023-03-23
0.0.155	11 / 7	2023-03-17
0.0.154	11 / 7	2023-03-16
0.0.153	11 / 7	2023-03-14
0.0.152	11 / 7	2023-03-11
0.0.151	11 / 7	2023-03-10
0.0.150	11 / 7	2023-03-09
0.0.149	11 / 7	2023-03-04
0.0.147	11 / 7	2023-03-03
0.0.145	11 / 7	2023-02-28
0.0.144	11 / 7	2023-02-09
0.0.143	11 / 7	2023-01-30
0.0.142	11 / 7	2023-01-27
0.0.141	11 / 7	2023-01-05
0.0.140	11 / 7	2022-12-13
0.0.139	11 / 7	2022-12-08

v0.0.161

1 finding

LOW No provenance attestation provenance

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

v0.0.160

1 finding

LOW No provenance attestation provenance

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

v0.0.159

1 finding

LOW No provenance attestation provenance

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

v0.0.158

1 finding

LOW No provenance attestation provenance

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

v0.0.157

1 finding

LOW No provenance attestation provenance

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

v0.0.156

1 finding

LOW No provenance attestation provenance

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

v0.0.155

1 finding

LOW No provenance attestation provenance

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

v0.0.154

1 finding

LOW No provenance attestation provenance

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

v0.0.153

1 finding

LOW No provenance attestation provenance

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

v0.0.152

1 finding

LOW No provenance attestation provenance

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

v0.0.151

1 finding

LOW No provenance attestation provenance

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

v0.0.150

1 finding

LOW No provenance attestation provenance

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

v0.0.149

1 finding

LOW No provenance attestation provenance

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

v0.0.147

1 finding

LOW No provenance attestation provenance

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

v0.0.145

1 finding

LOW No provenance attestation provenance

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

v0.0.144

1 finding

LOW No provenance attestation provenance

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

v0.0.143

1 finding

LOW No provenance attestation provenance

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

v0.0.142

1 finding

LOW No provenance attestation provenance

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

v0.0.141

1 finding

LOW No provenance attestation provenance

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

v0.0.140

1 finding

LOW No provenance attestation provenance

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

v0.0.139

1 finding

LOW No provenance attestation provenance

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