jQuery Mobile

Touch-Optimized Web Framework for Smartphones & Tablets

jquery-mobile@1.5.0-alpha.1 was published on 2017-04-13. 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.8.0.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All jQuery Mobile versions · Permanent reference to 1.5.0-alpha.1

Package specifications

Version1.5.0-alpha.1
License declarationNot declared
Published2017-04-13T17:57:39.554Z
Node.js requirement>= 0.8.0
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified size1.35 KiB
Minified + gzip713 B
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryGruntfile.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies1
Repository stars9592
Repository forks2348

Install jQuery Mobile 1.5.0-alpha.1

npm install jquery-mobile@1.5.0-alpha.1
pnpm add jquery-mobile@1.5.0-alpha.1
yarn add jquery-mobile@1.5.0-alpha.1

Runtime dependencies

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.

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.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — project is archived
Code-Review1/10 — Found 3/28 approved changesets -- score normalized to 1
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness