@react-google-maps/api
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:webpack | AI (phantom-deps): webpack listed as runtime dep but used only for build tooling; no exec/exfil behavior. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): False positive: @react-google-maps/api is a well-established Google Maps React wrapper with no relation to hapi. Edit-distance match is meaningless across scoped package names. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): False positive: @react-google-maps/api has no relation to the pg PostgreSQL client. Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): False positive: @react-google-maps/api has no relation to joi. Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): False positive: @react-google-maps/api has no relation to ajv. Levenshtein match is spurious. | ai | |
| phantom-deps | phantom-dep:@types/google.maps | AI (phantom-deps): @types/google.maps provides ambient TypeScript types for the Google Maps API; it is expected to be declared without direct imports in a TypeScript Google Maps wrapper. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 2.20.8 | 6 / 41 | |
| 2.20.7 | 6 / 41 | |
| 2.20.6 | 6 / 33 | |
| 2.20.5 | 6 / 33 | |
| 2.20.4 | 6 / 33 | |
| 2.20.3 | 6 / 33 | |
| 2.20.2 | 6 / 15 | |
| 2.20.1 | 6 / 15 | |
| 2.20.0 | 6 / 15 | |
| 2.19.3 | 6 / 14 | |
| 2.19.2 | 6 / 14 | |
| 2.19.0 | 6 / 14 | |
| 2.18.1 | 6 / 13 | |
| 2.17.1 | 6 / 13 | |
| 2.17.0 | 6 / 13 | |
| 2.16.1 | 6 / 13 | |
| 2.16.0 | 6 / 13 | |
| 2.15.0 | 6 / 13 | |
| 2.14.0 | 6 / 13 | |
| 2.13.1 | 6 / 13 | |
| 2.13.0 | 6 / 13 | |
| 2.12.2 | 6 / 13 | |
| 2.12.1 | 6 / 13 | |
| 2.12.0 | 6 / 13 | |
| 2.11.9 | 6 / 13 | |
| 2.11.8 | 6 / 13 | |
| 2.11.7 | 6 / 13 | |
| 2.11.6 | 6 / 13 | |
| 2.11.5 | 6 / 13 | |
| 2.11.4 | 6 / 13 | |
| 2.11.3 | 6 / 13 | |
| 2.11.2 | 6 / 13 | |
| 2.11.1 | 6 / 13 | |
| 2.10.3 | 6 / 13 | |
| 2.10.2 | 6 / 13 | |
| 2.10.1 | 6 / 13 | |
| 2.10.0 | 6 / 13 | |
| 2.8.1 | 6 / 55 | |
| 2.8.0 | 6 / 55 | |
| 2.7.0 | 6 / 49 | |
| 2.5.0 | 5 / 49 | |
| 2.4.1 | 5 / 49 | |
| 2.4.0 | 5 / 49 | |
| 2.3.0 | 5 / 50 | |
| 2.2.0 | 4 / 47 | |
| 2.1.1 | 4 / 47 | |
| 2.1.0 | 4 / 47 | |
| 2.0.2 | 4 / 46 | |
| 2.0.1 | 4 / 46 |
v2.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.