Jasmine 2.5.0
Command line jasmine
jasmine@2.5.0 was published on 2016-08-31. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All Jasmine versions · Permanent reference to 2.5.0 · Latest release
Package specifications
| Version | 2.5.0 |
|---|---|
| License declaration | MIT |
| Published | 2016-08-31T04:55:48.239Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| 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/jasmine.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 379 |
| Repository forks | 144 |
Install Jasmine 2.5.0
npm install jasmine@2.5.0 pnpm add jasmine@2.5.0 yarn add jasmine@2.5.0
Runtime dependencies
- exit ^0.1.2
- glob ^3.2.11
- jasmine-core ~2.5.0
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.
- exit@0.1.2 — direct
- glob@3.2.11 — direct
- inherits@2.0.4 — indirect
- jasmine-core@2.5.2 — direct
- lru-cache@2.7.3 — indirect
- minimatch@0.3.0 — indirect
- sigmund@1.0.1 — indirect
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.
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 10/10 — 17 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 |
| SAST | 0/10 — no SAST tool detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not 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 |
Evidence and freshness
- https://registry.npmjs.org/jasmine/2.5.0 — retrieved 2026-10-29T06:34:08.439Z
- https://api.deps.dev/v3/projects/github.com%2Fjasmine%2Fjasmine-npm — retrieved 2026-10-29T05:08:26.528Z
- https://api.deps.dev/v3/systems/npm/packages/jasmine/versions/2.5.0 — retrieved 2026-10-29T06:34:09.125Z
- https://api.deps.dev/v3/systems/npm/packages/jasmine/versions/2.5.0:dependencies — retrieved 2026-10-29T06:34:09.154Z