Packages

cors

2.8.6 · 22 Jan 2026MIT130.7M / weekRepositoryHomepagenpmAtom feed

Upgrading cors From 0.0.5 to 2.8.6

30 releases in betweennotes for 1

Reading releases, release notes and advisories…

Other targets from 0.0.5Newest 0.x0.1.1
2.0.0, 1.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below.
  1. 0.0.5yours
  2. 0.1.0major
  3. 1 release
  4. 1.0.0major
  5. 1 release
  6. 2.0.0major
  7. 24 releases
  8. 2.8.6target
?
changes to make
0
advisories fixed
1+
new
2+
fixes

Counted from 1 of 30 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 2.8.6

    22 Jan 20261 new · 2 fixes
    • New

      Added new link & website in the README

    • Fixed

      Fix functions call with extra parameter

    • Fixed

      :bug: Fix readme status badge

  2. 0.1.0 – 2.8.529 releases, no release note

7 other lines we could not sort, mostly version bumps
  • Update README.md for origin function callback parameters

    2.8.6
  • Suggest passing false for disallowed domains, not erroring

    2.8.6
  • Changed the term whitelist to allowlist in Documentation

    2.8.6
  • OSSF Scorecard recommendations

    2.8.6
  • Update the docs for per request config

    2.8.6
  • (fix): readme updated for #271 origin option for *

    2.8.6
  • Extend CI test matrix

    2.8.6

25 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.