You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I have noticed a minor security issue, reported by npm audit, regarding a dependency of this project. It's related to an older version of lodash@<4.17.5 allowing to pollute the prototype namespace by using the merge methods. The exact security report can be found here, https://nodesecurity.io/advisories/577. I also added the full report below.
I know that this project doesn't use lodash itself, but it does include an older version of react-google-maps. You can see this in de added dependency chain. This older version of react-google-maps includes the affected lodash dependency. Luckily, react-google-maps has fixed this issue in versions starting at 8.0.0.
Hi! I have noticed a minor security issue, reported by
npm audit
, regarding a dependency of this project. It's related to an older version oflodash@<4.17.5
allowing to pollute the prototype namespace by using the merge methods. The exact security report can be found here, https://nodesecurity.io/advisories/577. I also added the full report below.I know that this project doesn't use lodash itself, but it does include an older version of
react-google-maps
. You can see this in de added dependency chain. This older version ofreact-google-maps
includes the affected lodash dependency. Luckily,react-google-maps
has fixed this issue in versions starting at8.0.0
.I would recommend update this dependency to
>=8.0.0
, currently they are at9.4.5
. There is only 1 breaking change when migrating from7.3.0
to8.0.0
, one of which im not exactly sure if it affects this library (https://github.com/tomchentw/react-google-maps/blob/v8.0.0/CHANGELOG.md#breaking-changes).Let me know if I can do anything to help resolving this, by creating a PR for example. 😄
Cheers,
Cedric
The dependency chain
The full report by
npm audit
The text was updated successfully, but these errors were encountered: