← Home

@teambit/component.ui.component-compare.component-compare

npm Repository Homepage
83
Versions
—
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.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@teambit/base-react.navigation.link AI (dependencies): First-party @teambit package within the same monorepo ecosystem. ai
provenance publisher-changed AI (provenance): davidfirst is a long-standing teambit contributor with 250 approved packages; transition from teambit-owner is a legitimate org account change. ai
npm-metadata no-description AI (npm-metadata): Teambit component packages consistently omit descriptions; stable false positive for this package family. ai
provenance no-provenance AI (provenance): Teambit publishes without Sigstore provenance across all their packages; stable pattern. ai

Versions (showing 83 of 83)

Version Deps Published
0.0.269 18 / 8
0.0.268 18 / 8
0.0.267 18 / 8
0.0.266 17 / 3
0.0.265 17 / 3
0.0.264 17 / 3
0.0.263 17 / 3
0.0.262 17 / 3
0.0.261 17 / 3
0.0.260 17 / 3
0.0.259 17 / 3
0.0.258 17 / 3
0.0.257 17 / 3
0.0.256 17 / 3
0.0.255 17 / 3
0.0.254 17 / 3
0.0.253 16 / 3
0.0.252 16 / 3
0.0.251 16 / 3
0.0.250 16 / 3
0.0.249 16 / 3
0.0.248 16 / 3
0.0.247 16 / 3
0.0.246 16 / 3
0.0.245 16 / 3
0.0.244 16 / 3
0.0.243 16 / 3
0.0.242 16 / 3
0.0.241 16 / 3
0.0.240 16 / 3
0.0.239 16 / 3
0.0.238 16 / 3
0.0.237 16 / 3
0.0.236 16 / 3
0.0.235 16 / 3
0.0.234 16 / 3
0.0.233 16 / 3
0.0.232 16 / 3
0.0.231 16 / 3
0.0.230 16 / 3
0.0.228 16 / 3
0.0.227 16 / 3
0.0.226 16 / 3
0.0.225 16 / 3
0.0.224 16 / 3
0.0.223 16 / 3
0.0.222 17 / 3
0.0.221 17 / 3
0.0.220 16 / 3
0.0.218 16 / 3
0.0.217 16 / 3
0.0.216 16 / 3
0.0.215 16 / 3
0.0.214 16 / 3
0.0.213 16 / 3
0.0.211 17 / 3
0.0.210 17 / 3
0.0.209 16 / 3
0.0.208 16 / 3
0.0.207 16 / 3
0.0.206 16 / 3
0.0.205 16 / 3
0.0.204 16 / 3
0.0.203 16 / 3
0.0.202 16 / 3
0.0.201 16 / 3
0.0.200 16 / 3
0.0.199 16 / 3
0.0.198 16 / 3
0.0.197 16 / 3
0.0.196 16 / 3
0.0.194 16 / 3
0.0.193 16 / 3
0.0.192 16 / 3
0.0.191 16 / 3
0.0.190 16 / 3
0.0.189 16 / 3
0.0.188 16 / 3
0.0.187 16 / 3
0.0.185 16 / 3
0.0.184 16 / 3
0.0.183 16 / 3
0.0.182 16 / 3

v0.0.269

1 finding
INFO No provenance attestation provenance

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

v0.0.268

1 finding
INFO No provenance attestation provenance

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

v0.0.267

1 finding
INFO No provenance attestation provenance

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

v0.0.266

1 finding
INFO No provenance attestation provenance

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

v0.0.265

1 finding
INFO No provenance attestation provenance

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

v0.0.264

1 finding
INFO No provenance attestation provenance

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

v0.0.220

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-04-16, known maintainer) provenance

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

v0.0.218

1 finding
INFO No provenance attestation provenance

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

v0.0.217

1 finding
INFO No provenance attestation provenance

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

v0.0.216

1 finding
INFO No provenance attestation provenance

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

v0.0.215

1 finding
INFO No provenance attestation provenance

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

v0.0.214

1 finding
INFO No provenance attestation provenance

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

v0.0.213

1 finding
INFO No provenance attestation provenance

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

v0.0.211

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 2025-02-09, known maintainer) provenance

This version was published by a different npm account (shohamgilad) than the most recent previously approved version (davidfirst) on 2025-02-09, 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.

v0.0.210

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.

v0.0.209

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.

v0.0.208

1 finding
INFO No provenance attestation provenance

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

v0.0.207

1 finding
INFO No provenance attestation provenance

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

v0.0.206

1 finding
INFO No provenance attestation provenance

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

v0.0.205

1 finding
INFO No provenance attestation provenance

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

v0.0.204

1 finding
INFO No provenance attestation provenance

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

v0.0.203

1 finding
INFO No provenance attestation provenance

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

v0.0.202

1 finding
INFO No provenance attestation provenance

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

v0.0.201

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.

v0.0.200

1 finding
INFO No provenance attestation provenance

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

v0.0.199

1 finding
INFO No provenance attestation provenance

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

v0.0.198

1 finding
INFO No provenance attestation provenance

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

v0.0.197

1 finding
INFO No provenance attestation provenance

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

v0.0.196

1 finding
INFO No provenance attestation provenance

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

v0.0.194

1 finding
INFO No provenance attestation provenance

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

v0.0.193

1 finding
INFO No provenance attestation provenance

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

v0.0.192

1 finding
INFO No provenance attestation provenance

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

v0.0.191

1 finding
INFO No provenance attestation provenance

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

v0.0.190

1 finding
INFO No provenance attestation provenance

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

v0.0.189

1 finding
INFO No provenance attestation provenance

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

v0.0.188

1 finding
INFO No provenance attestation provenance

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

v0.0.187

1 finding
INFO No provenance attestation provenance

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

v0.0.185

1 finding
INFO No provenance attestation provenance

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

v0.0.184

1 finding
INFO No provenance attestation provenance

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

v0.0.183

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.

v0.0.182

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.