Native NodeJS implementation of MaxMind's GeoIP API -- works in node 0.6.3 and above, ask me about other versions
Installations
npm install geoip-lite
Developer Guide
Typescript
No
Module System
CommonJS
Min. Node Version
>=10.3.0
Node Version
18.18.2
NPM Version
10.3.0
Score
95.9
Supply Chain
98.7
Quality
74.7
Maintenance
100
Vulnerability
85.3
License
Releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (100%)
Developer
Download Statistics
Total Downloads
32,601,939
Last Day
27,485
Last Week
135,135
Last Month
650,235
Last Year
7,865,805
GitHub Statistics
2,344 Stars
264 Commits
359 Forks
42 Watching
2 Branches
49 Contributors
Bundle Size
31.41 kB
Minified
10.64 kB
Minified + Gzipped
Package Meta Information
Latest Version
1.4.10
Package Id
geoip-lite@1.4.10
Unpacked Size
153.12 MB
Size
41.83 MB
File Count
17
NPM Version
10.3.0
Node Version
18.18.2
Publised On
15 Feb 2024
Total Downloads
Cumulative downloads
Total Downloads
32,601,939
Last day
-10.4%
27,485
Compared to previous day
Last week
-21.8%
135,135
Compared to previous week
Last month
0.2%
650,235
Compared to previous month
Last year
17.1%
7,865,805
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
7
GeoIP-lite
A native NodeJS API for the GeoLite data from MaxMind.
This product includes GeoLite data created by MaxMind, available from http://maxmind.com/
NOTE You MUST update the data files after installation. The MaxMind license does not allow us to distribute the latest version of the data files with this package. Follow the instructions under update the datafiles for details.
introduction
MaxMind provides a set of data files for IP to Geo mapping along with opensource libraries to parse and lookup these data files. One would typically write a wrapper around their C API to get access to this data in other languages (like JavaScript).
GeoIP-lite instead attempts to be a fully native JavaScript library. A converter script converts the CSV files from MaxMind into an internal binary format (note that this is different from the binary data format provided by MaxMind). The geoip module uses this binary file to lookup IP addresses and return the country, region and city that it maps to.
Both IPv4 and IPv6 addresses are supported, however since the GeoLite IPv6 database does not currently contain any city or region information, city, region and postal code lookups are only supported for IPv4.
philosophy
I was really aiming for a fast JavaScript native implementation for geomapping of IPs. My prime motivator was the fact that it was really hard to get libgeoip built for Mac OSX without using the library from MacPorts.
why geoip-lite
geoip-lite
is a fully JavaScript implementation of the MaxMind geoip API. It is not as fully featured as bindings that use libgeoip
.
By reducing scope, this package is about 40% faster at doing lookups. On average, an IP to Location lookup should take 20 microseconds on
a Macbook Pro. IPv4 addresses take about 6 microseconds, while IPv6 addresses take about 30 microseconds.
synopsis
1var geoip = require('geoip-lite'); 2 3var ip = "207.97.227.239"; 4var geo = geoip.lookup(ip); 5 6console.log(geo); 7{ range: [ 3479298048, 3479300095 ], 8 country: 'US', 9 region: 'TX', 10 eu: '0', 11 timezone: 'America/Chicago', 12 city: 'San Antonio', 13 ll: [ 29.4969, -98.4032 ], 14 metro: 641, 15 area: 1000 } 16
installation
1. get the library
$ npm install geoip-lite
2. update the datafiles (optional)
Run cd node_modules/geoip-lite && npm run-script updatedb license_key=YOUR_LICENSE_KEY
to update the data files. (Replace YOUR_LICENSE_KEY
with your license key obtained from maxmind.com)
You can create a maxmind account here
NOTE that this requires a lot of RAM. It is known to fail on on a Digital Ocean or AWS micro instance.
There are no plans to change this. geoip-lite
stores all data in RAM in order to be fast.
API
geoip-lite is completely synchronous. There are no callbacks involved. All blocking file IO is done at startup time, so all runtime calls are executed in-memory and are fast. Startup may take up to 200ms while it reads into memory and indexes data files.
Looking up an IP address
If you have an IP address in dotted quad notation, IPv6 colon notation, or a 32 bit unsigned integer (treated
as an IPv4 address), pass it to the lookup
method. Note that you should remove any [
and ]
around an
IPv6 address before passing it to this method.
1var geo = geoip.lookup(ip);
If the IP address was found, the lookup
method returns an object with the following structure:
1{ 2 range: [ <low bound of IP block>, <high bound of IP block> ], 3 country: 'XX', // 2 letter ISO-3166-1 country code 4 region: 'RR', // Up to 3 alphanumeric variable length characters as ISO 3166-2 code 5 // For US states this is the 2 letter state 6 // For the United Kingdom this could be ENG as a country like “England 7 // FIPS 10-4 subcountry code 8 eu: '0', // 1 if the country is a member state of the European Union, 0 otherwise. 9 timezone: 'Country/Zone', // Timezone from IANA Time Zone Database 10 city: "City Name", // This is the full city name 11 ll: [<latitude>, <longitude>], // The latitude and longitude of the city 12 metro: <metro code>, // Metro code 13 area: <accuracy_radius> // The approximate accuracy radius (km), around the latitude and longitude 14}
The actual values for the range
array depend on whether the IP is IPv4 or IPv6 and should be
considered internal to geoip-lite
. To get a human readable format, pass them to geoip.pretty()
If the IP address was not found, the lookup
returns null
Pretty printing an IP address
If you have a 32 bit unsigned integer, or a number returned as part of the range
array from the lookup
method,
the pretty
method can be used to turn it into a human readable string.
1 console.log("The IP is %s", geoip.pretty(ip));
This method returns a string if the input was in a format that geoip-lite
can recognise, else it returns the
input itself.
Built-in Updater
This package contains an update script that can pull the files from MaxMind and handle the conversion from CSV. A npm script alias has been setup to make this process easy. Please keep in mind this requires internet and MaxMind rate limits that amount of downloads on their servers.
You will need, at minimum, a free license key obtained from maxmind.com to run the update script.
Package stores checksums of MaxMind data and by default only downloads them if checksums have changed.
Ways to update data
1#update data if new data is available 2npm run-script updatedb license_key=YOUR_LICENSE_KEY 3 4#force udpate data even if checkums have not changed 5npm run-script updatedb-force license_key=YOUR_LICENSE_KEY
You can also run it by doing:
1node ./node_modules/geoip-lite/scripts/updatedb.js license_key=YOUR_LICENSE_KEY
Ways to reload data in your app when update finished
If you have a server running geoip-lite
, and you want to reload its geo data, after you finished update, without a restart.
Programmatically
You can do it programmatically, calling after scheduled data updates
1//Synchronously 2geoip.reloadDataSync(); 3 4//Asynchronously 5geoip.reloadData(function(){ 6 console.log("Done"); 7});
Automatic Start and stop watching for data updates
You can enable the data watcher to automatically refresh in-memory geo data when a file changes in the data directory.
1geoip.startWatchingDataUpdate();
This tool can be used with npm run-script updatedb
to periodically update geo data on a running server.
Environment variables
The following environment variables can be set.
1# Override the default node_modules/geoip-lite/data dir 2GEOTMPDIR=/some/path 3 4# Override the default node_modules/geoip-lite/tmp dir 5GEODATADIR=/some/path
Caveats
This package includes the GeoLite database from MaxMind. This database is not the most accurate database available,
however it is the best available for free. You can use the commercial GeoIP database from MaxMind with better
accuracy by buying a license from MaxMind, and then using the conversion utility to convert it to a format that
geoip-lite understands. You will need to use the .csv
files from MaxMind for conversion.
Also note that on occassion, the library may take up to 5 seconds to load into memory. This is largely dependent on how busy your disk is at that time. It can take as little as 200ms on a lightly loaded disk. This is a one time cost though, and you make it up at run time with very fast lookups.
Memory usage
Quick test on memory consumption shows that library uses around 100Mb per process
1 var geoip = require('geoip-lite'); 2 console.log(process.memoryUsage()); 3 /** 4 * Outputs: 5 * { 6 * rss: 126365696, 7 * heapTotal: 10305536, 8 * heapUsed: 5168944, 9 * external: 104347120 10 * } 11 **/
Alternatives
If your use-case requires doing less than 100 queries through the lifetime of your application or if you need really fast latency on start-up, you might want to look into fast-geoip a package with a compatible API that is optimized for serverless environments and provides faster boot times and lower memory consumption at the expense of longer lookup times.
References
Copyright
geoip-lite
is Copyright Philip Tellis philip@bluesmoon.info and other contributors, and the latest version of the code is
available at https://github.com/bluesmoon/node-geoip
License
There are two licenses for the code and data. See the LICENSE file for details.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Reason
Found 13/30 approved changesets -- score normalized to 4
Reason
0 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 1
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/geoip-lite/node-geoip/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/geoip-lite/node-geoip/test.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:18
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 14 are checked with a SAST tool
Score
4.3
/10
Last Scanned on 2025-01-27
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn MoreOther packages similar to geoip-lite
@types/geoip-lite
TypeScript definitions for geoip-lite
@codebet/geoip-lite-auto-update
A light weight native JavaScript implementation of GeoIP API from MaxMind
fast-geoip
A faster & low-memory replacement for geoip-lite, a node library that maps IPs to geographical information
@basicer/geoip-lite
A light weight native JavaScript implementation of GeoIP API from MaxMind