cors 2.5.3
middleware for dynamically or statically enabling CORS in express/connect applications
cors@2.5.3 was published on 2015-01-20. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All cors versions · Permanent reference to 2.5.3 · Latest release
Package specifications
| Version | 2.5.3 |
|---|---|
| License declaration | Not declared |
| Published | 2015-01-20T21:52:22.113Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./lib/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 6195 |
| Repository forks | 518 |
Install cors 2.5.3
npm install cors@2.5.3 pnpm add cors@2.5.3 yarn add cors@2.5.3
Runtime dependencies
- vary ^1
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- vary@1.1.2 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Maintained | 0/10 — 0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0 |
| Code-Review | 9/10 — Found 18/19 approved changesets -- score normalized to 9 |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Pinned-Dependencies | 6/10 — dependency not pinned by hash detected -- score normalized to 6 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 8/10 — SAST tool detected but not run on all commits |
Evidence and freshness
- https://registry.npmjs.org/cors/2.5.3 — retrieved 2026-10-29T09:57:44.882Z
- https://api.deps.dev/v3/projects/github.com%2Fexpressjs%2Fcors — retrieved 2026-10-29T05:55:19.427Z
- https://api.deps.dev/v3/systems/npm/packages/cors/versions/2.5.3 — retrieved 2026-10-29T09:57:45.409Z
- https://api.deps.dev/v3/systems/npm/packages/cors/versions/2.5.3:dependencies — retrieved 2026-10-29T09:57:45.405Z