@momentum-ui/web-components
[](https://github.com/momentum-design/momentum-ui/blob/main/LICENSE) [: 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 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.2.22 | 17 / 0 | |
| 3.2.21 | 17 / 0 | |
| 3.2.20 | 17 / 0 | |
| 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 | |
| 3.2.12 | 17 / 0 | |
| 3.2.11 | 17 / 0 | |
| 3.2.10 | 17 / 0 | |
| 3.2.9 | 17 / 0 | |
| 3.2.8 | 17 / 0 | |
| 3.2.7 | 17 / 0 | |
| 3.2.6 | 17 / 0 | |
| 3.2.5 | 17 / 0 | |
| 3.2.4 | 17 / 0 | |
| 3.2.3 | 17 / 0 | |
| 3.2.2 | 17 / 0 | |
| 3.2.1 | 17 / 0 | |
| 3.2.0 | 17 / 0 |
v3.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.