@momentum-ui/web-components
[](https://github.com/momentum-design/momentum-ui/blob/main/LICENSE) [ relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@interactjs/core | AI (dependencies): interact.js is a well-known drag-and-drop library; stable legitimate dependency for this UI component package. | ai | |
| dependencies | unvetted-dep:@interactjs/interact | AI (dependencies): Part of the interact.js suite; same rationale as @interactjs/core. | ai | |
| dependencies | unvetted-dep:country-flags-svg | AI (dependencies): Known utility library for country flag SVGs; appropriate for a UI components package with phone/country features. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large UI component library; README linking to many component docs is expected, not a link farm. | ai | |
| phantom-deps | phantom-dep:@interactjs/utils | AI (phantom-deps): Same interactjs facade pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:json | AI (phantom-deps): json is a declared runtime dep used in build/config tooling; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| phantom-deps | phantom-dep:@interactjs/core | AI (phantom-deps): interactjs packages are used via the interact.js facade; direct import of sub-packages not required. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.2.19 | 17 / 0 | |
| 3.2.17 | 17 / 0 | |
| 3.2.16 | 17 / 0 | |
| 3.2.15 | 17 / 0 | |
| 3.2.14 | 17 / 0 | |
| 3.2.13 | 17 / 0 |
v3.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.