geoip-country
Quick country lookup from IP address
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in the database update utility script, not in any install hook. Expected for a GeoIP package that downloads and processes MaxMind data files. | ai | |
| dependencies | unvetted-dep:countries-list | AI (dependencies): countries-list is a well-known npm package for country metadata; its use in a GeoIP country lookup library is entirely appropriate. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 5.0.202605230000 | 4 / 3 | |
| 5.0.202605200000 | 4 / 3 | |
| 5.0.202605152358 | 4 / 3 | |
| 5.0.202605122359 | 4 / 3 | |
| 5.0.202605082359 | 4 / 3 | |
| 5.0.202605052357 | 4 / 3 | |
| 5.0.202605012358 | 4 / 3 | |
| 5.0.202604282358 | 4 / 3 | |
| 5.0.202604242354 | 4 / 3 | |
| 5.0.202604212352 | 4 / 3 | |
| 5.0.202604172354 | 4 / 3 | |
| 5.0.202604142355 | 4 / 3 | |
| 5.0.202604102352 | 4 / 3 | |
| 5.0.202604072353 | 4 / 3 | |
| 5.0.202604032350 | 4 / 3 | |
| 5.0.202603312350 | 4 / 3 | |
| 5.0.202603272348 | 4 / 3 | |
| 5.0.202512052343 | 4 / 3 | |
| 5.0.202512022343 | 4 / 3 | |
| 5.0.202511282342 | 4 / 3 | |
| 5.0.202511252342 | 4 / 3 | |
| 5.0.202511212342 | 4 / 3 | |
| 5.0.202511182342 | 4 / 3 | |
| 5.0.202511142342 | 4 / 3 | |
| 5.0.202511112342 | 4 / 3 | |
| 5.0.202511072342 | 4 / 3 | |
| 5.0.202511042342 | 4 / 3 | |
| 5.0.202510312342 | 4 / 3 | |
| 5.0.202510282342 | 4 / 3 | |
| 4.2.262 | 5 / 1 | |
| 4.2.261 | 5 / 1 | |
| 4.2.260 | 5 / 1 | |
| 4.2.259 | 5 / 1 | |
| 4.2.258 | 5 / 1 | |
| 4.2.257 | 5 / 1 | |
| 4.2.256 | 5 / 1 | |
| 4.2.255 | 5 / 1 | |
| 4.2.254 | 5 / 1 | |
| 4.2.253 | 5 / 1 | |
| 4.2.252 | 5 / 1 | |
| 4.2.251 | 5 / 1 |
v5.0.202605230000
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202605200000
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202605152358
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202605122359
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202605082359
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202605052357
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202605012358
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604282358
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604242354
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604212352
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604172354
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604142355
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604102352
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604072353
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202604032350
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202603312350
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202603272348
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.202512052343
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202512022343
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511282342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511252342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511212342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511182342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511142342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511112342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511072342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202511042342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202510312342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.202510282342
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.262
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.260
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.259
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.258
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.257
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.256
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.255
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.254
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.253
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.252
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.251
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.