Homepage

@visx/geo vulnerabilities

visx geo
Licenses: MIT
Published: 5 years ago Last updated: 1 years ago Latest version: 3.12.0 Latest non-vulnerable version: 4.0.1-alpha.0
npm
GitHub

Package Health Score

81/100
  • securityNo known security issues
  • popularityInfluential project
  • maintenanceInactive
  • communityActive

Maintenance

INACTIVE

Commit Frequency

Loading chart...

Open Issues
119
Open PR
28
New PRS
1
Last Release
1 years ago
Last Commit
3 months ago
Maintainers
3

Further analysis of the maintenance status of @visx/geo based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @visx/geo is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Popularity

INFLUENTIAL PROJECT
Weekly downloads (126.2k)
GitHub Stars
20.6k
Forks
755
Contributors
170

The npm package @visx/geo receives a total of 126,201 downloads a week. As such, we scored @visx/geo popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @visx/geo, we found that it has been starred 20,597 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

ACTIVE
Readme.md
No
Contributing.md
Yes
Code of Conduct
Yes
Contributors
170
Funding
No
LICENSE
MIT

A good and healthy external contribution signal for @visx/geo project, which invites more than one hundred open source maintainers to collaborate on the repository.

How about a good first contribution to this project? It seems that @visx/geo is missing a README file.

License

MIT>=0;
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

No direct vulnerabilities have been found for this package in Snyk’s vulnerability database. This does not include vulnerabilities belonging to this package’s dependencies.

Does your project rely on vulnerable package dependencies?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities (in both your packages & their dependencies) and provides automated fixes for free.

Scan for indirect vulnerabilities

Security

NO KNOWN SECURITY ISSUES
Show only direct vulnerabilities in latest version
No vulnerabilities found

No vulnerabilities found in the latest version

Package versions

21 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
4.0.1-alpha.011 Nov, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
4.0.0-alpha.010 Nov, 2025
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.13.0-alpha.016 Dec, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.12.07 Nov, 2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.5.013 Nov, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.3.011 Jul, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.0.06 Jan, 2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
3.0.0-alpha.010 Aug, 2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.17.022 Dec, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.17.0-alpha.021 Dec, 2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

@visx/geo dependencies

6 IN TOTAL
classnamesprop-types@visx/group@types/react@visx/vendor@types/geojson

@visx/geo development dependencies

2 IN TOTAL
topojson-client@types/topojson-client