libphonenumber-js
A simpler (and smaller) rewrite of Google Android's libphonenumber library in javascript
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:mobile/examples/examples.mobile.json.js | AI (source-diff): Single-line JSON exported as ES module for browser compatibility (documented workaround for issue #239). Contains readable phone example data, not obfuscated code. | ai | |
| source-diff | obfuscated-file:max/metadata/metadata.max.json.js | AI (source-diff): Single-line JSON exported as ES module for browser compatibility (documented workaround for issue #239). Contains readable phone metadata, not obfuscated code. | ai | |
| source-diff | obfuscated-file:min/metadata/metadata.min.json.js | AI (source-diff): Single-line JSON exported as ES module for browser compatibility (documented workaround for issue #239). Contains readable phone metadata, not obfuscated code. | ai | |
| source-diff | obfuscated-file:mobile/metadata/metadata.mobile.json.js | AI (source-diff): Single-line JSON exported as ES module for browser compatibility (documented workaround for issue #239). Contains readable phone metadata, not obfuscated code. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in runnable/modules/exec.js, a dev-only build utility for downloading/generating phone metadata. Not a runtime dependency; stable pattern for this package. | ai |
Versions (showing 100 of 447)
| Version | Deps | Published |
|---|---|---|
| 1.13.4 | 0 / 27 | |
| 1.13.3 | 0 / 27 | |
| 1.13.2 | 0 / 27 | |
| 1.13.1 | 0 / 27 | |
| 1.13.0 | 0 / 27 | |
| 1.12.43 | 0 / 27 | |
| 1.12.42 | 0 / 27 | |
| 1.12.41 | 0 / 27 | |
| 1.12.40 | 0 / 27 | |
| 1.12.39 | 0 / 27 | |
| 1.12.38 | 0 / 27 | |
| 1.12.37 | 0 / 27 | |
| 1.12.36 | 0 / 27 | |
| 1.12.35 | 0 / 27 | |
| 1.12.34 | 0 / 27 | |
| 1.12.33 | 0 / 27 | |
| 1.12.31 | 0 / 27 | |
| 1.12.30 | 0 / 27 | |
| 1.12.29 | 0 / 27 | |
| 1.12.28 | 0 / 27 | |
| 1.12.27 | 0 / 27 | |
| 1.12.26 | 0 / 27 | |
| 1.12.25 | 0 / 27 | |
| 1.12.24 | 0 / 27 | |
| 1.12.23 | 0 / 27 | |
| 1.12.22 | 0 / 27 | |
| 1.12.21 | 0 / 27 | |
| 1.12.18 | 0 / 26 | |
| 1.12.17 | 0 / 26 | |
| 1.12.16 | 0 / 26 | |
| 1.12.15 | 0 / 26 | |
| 1.12.14 | 0 / 26 | |
| 1.12.13 | 0 / 26 | |
| 1.12.12 | 0 / 26 | |
| 1.12.11 | 0 / 26 | |
| 1.12.10 | 0 / 23 | |
| 1.12.9 | 0 / 23 | |
| 1.12.8 | 0 / 23 | |
| 1.12.7 | 0 / 23 | |
| 1.12.6 | 0 / 23 | |
| 1.12.5 | 0 / 23 | |
| 1.12.4 | 0 / 23 | |
| 1.12.3 | 0 / 23 | |
| 1.12.2 | 0 / 23 | |
| 1.12.1 | 0 / 23 | |
| 1.12.0 | 0 / 23 | |
| 1.11.20 | 0 / 23 | |
| 1.11.19 | 0 / 23 | |
| 1.11.18 | 0 / 23 | |
| 1.11.17 | 0 / 23 | |
| 1.11.16 | 0 / 23 | |
| 1.11.15 | 0 / 23 | |
| 1.11.14 | 0 / 23 | |
| 1.11.13 | 0 / 23 | |
| 1.11.12 | 0 / 23 | |
| 1.11.11 | 0 / 23 | |
| 1.11.10 | 0 / 23 | |
| 1.11.9 | 0 / 23 | |
| 1.11.8 | 0 / 23 | |
| 1.11.7 | 0 / 23 | |
| 1.11.6 | 0 / 23 | |
| 1.11.5 | 0 / 23 | |
| 1.11.4 | 0 / 23 | |
| 1.11.3 | 0 / 23 | |
| 1.11.2 | 0 / 23 | |
| 1.11.1 | 0 / 23 | |
| 1.11.0 | 0 / 23 | |
| 1.10.64 | 0 / 23 | |
| 1.10.63 | 0 / 23 | |
| 1.10.62 | 0 / 23 | |
| 1.10.61 | 0 / 23 | |
| 1.10.60 | 0 / 23 | |
| 1.10.59 | 0 / 23 | |
| 1.10.58 | 0 / 23 | |
| 1.10.57 | 0 / 23 | |
| 1.10.56 | 0 / 23 | |
| 1.10.55 | 0 / 23 | |
| 1.10.54 | 0 / 23 | |
| 1.10.53 | 0 / 23 | |
| 1.10.52 | 0 / 23 | |
| 1.10.51 | 0 / 23 | |
| 1.10.50 | 0 / 23 | |
| 1.10.49 | 0 / 22 | |
| 1.10.48 | 0 / 22 | |
| 1.10.47 | 0 / 22 | |
| 1.10.46 | 0 / 22 | |
| 1.10.45 | 0 / 22 | |
| 1.10.44 | 0 / 22 | |
| 1.10.43 | 0 / 22 | |
| 1.10.42 | 0 / 22 | |
| 1.10.41 | 0 / 22 | |
| 1.10.40 | 0 / 22 | |
| 1.10.39 | 0 / 20 | |
| 1.10.38 | 0 / 20 | |
| 1.10.37 | 0 / 20 | |
| 1.10.36 | 0 / 20 | |
| 1.10.34 | 0 / 20 | |
| 1.10.33 | 0 / 20 | |
| 1.10.32 | 0 / 20 | |
| 1.10.31 | 0 / 20 |
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.13
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.12
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.