@teambit/component-compare
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer list cleanup in large monorepo, no new maintainer added, trusted publisher. | ai | |
| dependencies | unvetted-dep:@teambit/scope.objects | AI (dependencies): Same-org Teambit dependency, standard monorepo pattern. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo packages publish in lockstep within minutes; consistent with prior approved versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @teambit/schema from the same org/monorepo at matching version; consistent with routine teambit releases. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.constants | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.component-diff | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/legacy.consumer-component | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/ui-foundation.ui.menu-widget-icon | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/ui-foundation.ui.react-router.slot-router | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component.ui.component-compare.component-compare | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component.ui.component-compare.models.component-compare-props | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component.ui.component-compare.compare-aspects.compare-aspects | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component.ui.component-compare.models.component-compare-change-type | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component.ui.component-compare.changelog | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): First-party @teambit org dep from the teambit/bit monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| dependencies | unvetted-dep:@teambit/component-id | AI (dependencies): First-party @teambit org dep; stable pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established teambit monorepo package; missing description is a consistent pattern across their packages. | ai | |
| phantom-deps | phantom-dep:@teambit/legacy.consumer-component | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is unreliable for monorepo packages with re-exported types. | ai | |
| provenance | no-provenance | AI (provenance): teambit publishes without Sigstore provenance consistently across all versions. | ai |
Versions (showing 11 of 111)
| Version | Deps | Published |
|---|---|---|
| 1.0.267 | 24 / 4 | |
| 1.0.266 | 24 / 4 | |
| 1.0.265 | 24 / 4 | |
| 1.0.264 | 23 / 4 | |
| 1.0.263 | 23 / 4 | |
| 1.0.262 | 23 / 4 | |
| 1.0.261 | 23 / 4 | |
| 1.0.260 | 23 / 4 | |
| 1.0.259 | 23 / 4 | |
| 1.0.258 | 23 / 4 | |
| 1.0.257 | 23 / 4 |
v1.0.267
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.266
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.265
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.264
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.263
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.262
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.261
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.260
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.259
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.258
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (shohamgilad) than the most recent previously approved version (davidfirst) on 2024-04-30, 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.257
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.