@megafon/ui-core
React UI components library.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@megafon/ui-helpers | AI (phantom-deps): Same org scope; stable sibling dependency pattern. | ai | |
| phantom-deps | phantom-dep:@mona-health/react-input-mask | AI (phantom-deps): UI library; input mask referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:@datepicker-react/hooks | AI (phantom-deps): UI library with date components; referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:simplebar-react | AI (phantom-deps): UI library; simplebar referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/sortable | AI (phantom-deps): UI library with drag-and-drop; referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:react-transition-group | AI (phantom-deps): UI component library; transition dep referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:swiper | AI (phantom-deps): Large UI library; deps referenced in config/docs, not direct imports. Stable pattern. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Known implicit runtime polyfill dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): UI library with date components; referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:react-modal | AI (phantom-deps): UI component library; modal dep referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:react-popper | AI (phantom-deps): UI component library; popper dep referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): UI library with drag-and-drop; referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): UI library; lodash utilities referenced in config, stable pattern. | ai | |
| phantom-deps | phantom-dep:lodash.throttle | AI (phantom-deps): UI library; lodash utilities referenced in config, stable pattern. | ai | |
| dependencies | unvetted-dep:peerdeps | AI (dependencies): peerdeps is a standard peer-dependency installer utility; stable use in this package. | ai | |
| dependencies | unvetted-dep:@megafon/ui-helpers | AI (dependencies): First-party MegaFon helper package; consistent with this org's component library. | ai | |
| dependencies | unvetted-dep:@mona-health/react-input-mask | AI (dependencies): Known React input-mask fork; legitimate UI dependency for a component library. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with 482 versions; lack of provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): @popperjs/core is a peer/indirect dep of react-popper; phantom-dep heuristic fires but it is legitimately declared. | ai | |
| phantom-deps | phantom-dep:simplebar | AI (phantom-deps): simplebar is a runtime dep used via CSS/side-effects, not a direct JS import; stable false positive. | ai | |
| phantom-deps | phantom-dep:peerdeps | AI (phantom-deps): peerdeps is a tooling dep used in config/scripts, not a runtime import; stable false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 9.4.0 | 18 / 39 | |
| 9.3.0 | 18 / 39 | |
| 9.2.2 | 18 / 39 | |
| 9.1.0 | 18 / 39 | |
| 9.0.0 | 18 / 39 | |
| 8.17.4 | 18 / 39 | |
| 8.17.1 | 18 / 39 | |
| 8.16.3 | 18 / 39 | |
| 8.16.1 | 18 / 39 | |
| 8.16.0 | 18 / 39 | |
| 8.15.1 | 18 / 39 | |
| 8.15.0 | 18 / 39 |
v9.4.0
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 (dmitrylobasov) than the most recent previously approved version (myfka) on 2026-06-01, but dmitrylobasov 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.
v9.3.0
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 (myfka) than the most recent previously approved version (balffr) on 2026-05-27, but myfka 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.
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.