← Home

@ip-location-db/dbip-country-mmdb

npm Repository Homepage

Ip to location database

6
Versions
SEE LICENSE IN DBIP-LICENSE (CC-BY-4.0)
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

sapics

Keywords

ipip-locationip-location-dbipv4ipv6locationcountrymmdb

Versions (showing 6 of 6)

Version Deps Published
2.3.2026060120 0 / 0
2.3.2026050119 0 / 0
2.3.2026040119 0 / 0
2.3.2026030119 0 / 0
2.3.2026020119 0 / 0
2.3.2025120119 0 / 0

v2.3.2026040119

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.2026030119

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.3.2026020119

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: sapics → GitHub Actions (on 2026-02-01, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (sapics) on 2026-02-01, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v2.3.2025120119

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.