googlemaps
A simple way to query the Google Maps API from Node.js
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Long-established package with clean version diff; missing gitHead is a publish environment change, not a security indicator for this package. | ai | |
| provenance | no-provenance | AI (provenance): Older package predating Sigstore provenance; no CI/CD provenance is expected for this package's era and maintenance style. | ai | |
| typosquat | typosquat.levenshtein:googleapis | AI (typosquat): googlemaps is a legitimate, long-established (~15yr) Google Maps API client for Node.js — distinct from googleapis. Levenshtein proximity is coincidental, not a typosquat. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): check-types is a well-known, legitimate type-checking utility; its addition is consistent with input validation improvements in a Maps API wrapper. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): request is a well-known HTTP library and a legitimate, expected dependency for a Google Maps API HTTP client. Stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.12.0 | 4 / 2 | |
| 1.11.1 | 4 / 2 | |
| 1.11.0 | 4 / 2 | |
| 1.9.0 | 4 / 2 | |
| 1.3.0 | 4 / 3 | |
| 1.1.0 | 3 / 3 | |
| 1.0.2 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.1.15 | 2 / 1 | |
| 0.1.12 | 2 / 1 | |
| 0.1.6 | 1 / 1 | |
| 0.1.5 | 0 / 1 | |
| 0.1.4 | 0 / 1 | |
| 0.1.3 | 0 / 1 | |
| 0.1.2 | 0 / 1 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fabmos.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fabmos.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.