@megafon/ui-helpers
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:htmr | AI (phantom-deps): Direct runtime dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Direct runtime dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Known implicit dependency; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 4 / 15 | |
| 5.0.0 | 4 / 15 | |
| 4.1.3 | 4 / 15 | |
| 4.1.1 | 4 / 15 | |
| 4.1.0 | 4 / 15 |
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.