Homepage

@next/polyfill-nomodule vulnerabilities

A polyfill for non-dead, nomodule browsers.
Licenses: MIT
Published: 6 years ago Last updated: 14 days ago Latest version: 16.1.6 Latest non-vulnerable version: 16.2.0-canary.35
npm
GitHub

Package Health Score

95/100
  • securityNo known security issues
  • popularityPopular
  • maintenanceHealthy
  • communityActive

Maintenance

HEALTHY

Commit Frequency

Loading chart...

Open Issues
2040
Open PR
1208
New PRS
1
Last Release
14 days ago
Last Commit
11 days ago
Maintainers
5

Further analysis of the maintenance status of @next/polyfill-nomodule based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @next/polyfill-nomodule demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Popularity

POPULAR
Weekly downloads (15.4k)
GitHub Stars
137.4k
Forks
30.4k
Contributors
430

The npm package @next/polyfill-nomodule receives a total of 15,431 downloads a week. As such, we scored @next/polyfill-nomodule popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @next/polyfill-nomodule, we found that it has been starred 137,428 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

ACTIVE
Readme.md
No
Contributing.md
Yes
Code of Conduct
Yes
Contributors
430
Funding
No
LICENSE
MIT

A good and healthy external contribution signal for @next/polyfill-nomodule project, which invites more than one hundred open source maintainers to collaborate on the repository.

How about a good first contribution to this project? It seems that @next/polyfill-nomodule is missing a README file.

License

MIT>=0;
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

No direct vulnerabilities have been found for this package in Snyk’s vulnerability database. This does not include vulnerabilities belonging to this package’s dependencies.

Does your project rely on vulnerable package dependencies?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities (in both your packages & their dependencies) and provides automated fixes for free.

Scan for indirect vulnerabilities

Security

NO KNOWN SECURITY ISSUES
Show only direct vulnerabilities in latest version
No vulnerabilities found

No vulnerabilities found in the latest version

Package versions

2958 VERSIONS IN TOTAL See all versions
versionpublisheddirect vulnerabilities
16.2.0-canary.3510 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.3410 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.339 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.328 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.317 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.306 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.295 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.285 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.274 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
16.2.0-canary.263 Feb, 2026
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

@next/polyfill-nomodule development dependencies

4 IN TOTAL
core-jsmicrobundlewhatwg-fetchobject-assign