Skip to content

Upgrade nanoid to 3.3.18 #16

Openg1tbot wants to merge g1t/security/nanoid-3.3.18 into masterdependenciesjavascript

Other work is changing the same files

Whichever merges second will have to catch up, and may conflict.

g1tbotopened this pull request

Upgrades nanoid (npm) from 3.3.6 to 3.3.18, which fixes these known vulnerabilities:

AdvisorySeverityAffectedFixed inSummary
GHSA-28wg-ghj8-5hjvhigh3.3.63.3.16nanoid: non-secure generators can loop indefinitely with negative size
GHSA-2v37-7h3g-55p8high3.3.63.3.18nanoid: custom generators can loop indefinitely when size is zero
GHSA-mwcw-c2x4-8c55medium3.3.63.3.8Predictable results in nanoid generation when given non-integer values
GHSA-xwg4-73v4-xw9whigh3.3.63.3.12nanoid: Integer Overflow or Wraparound

Lockfiles changed: src/package-lock.json.

Only the version changes. This pull request lands through this branch's required checks like any other. If they fail because code has to change, g1t closes it and puts g1t on an issue to make the change.


Opened by g1t's security updates. Turn them off for this project on its Security page.

g1tbotadded the dependencies and javascript labels·
g1tbotcommented

Dependency review

Passed. 2 dependency changes, none vulnerable.

src/package-lock.json

ChangePackageVersionRelationshipLicenseVulnerabilities
Addednanoid3.3.20transitiveMITnone known
Removednanoid3.3.6transitiveunknown

This check fails on vulnerabilities of high severity or higher. Change it in the repository's Security settings.

All checks have passed

2 passed · none are required, so none hold the merge

Workflows

Dependency review — 2 dependency changes, none vulnerableDetails
g1t / deploy — Preview is live

No reviews yet

Up to date with master

Sign in to comment.