IFM

Single script file manager.

Slowing · 49
49/100
Slowing

Activity has dropped noticeably. Check the repository before committing to it.

Maintenance 6/40
Releases 25/25
Community 4/20
Momentum 15/15

Commit activity more than 14% of tracked projects; popularity more than 19%. How this is calculated.

Commits, last 11 months

2025-10: 0 commits 2025-11: 0 commits 2025-12: 8 commits 2026-01: 0 commits 2026-02: 0 commits 2026-03: 0 commits 2026-04: 0 commits 2026-05: 6 commits 2026-06: 1 commits 2026-07: 0 commits 2026-08: 14 commits
2025-10 29 total 2026-08
Stars370
Latest releasev4.1.2 · 20 Aug 2026
Repo updated20 Aug 2026
LicenceMIT
Built withPHP

Is IFM actively maintained?

Over the last 11 months the project absorbed 29 commits, of which 15 arrived in the most recent quarter — roughly 5 commits a month.

Activity is accelerating: the last quarter carried 150% more commits than the one before it.

The most recent tagged release, v4.1.2, shipped within the last month — a current, installable version exists today.

IFM ranks #9 of 17 in File Transfer - Web-based File Managers, placing it mid-table for maintenance activity.

What IFM actually does

IFM is a file manager distributed as a single script, designed for managing files directly on a server through a web interface. It provides basic web-based file transfer and organisation capabilities without requiring a complex installation procedure. Because the official documentation is sparse, users can expect standard directory browsing, upload, and download functions typical of lightweight PHP file management tools.

Best fit: This tool is a good fit for quick, temporary deployment when you need an immediate web-based file interface on a server without setting up a heavier platform.

Worth knowing: Single-script file managers often present significant security risks if exposed to the public internet without strict access controls. Furthermore, development activity is slowing, which may lead to unpatched vulnerabilities over time.

Deployment notes

Deployment typically requires a standard PHP runtime environment on your web server with appropriate read and write permissions for the directory. You should ensure proper TLS termination via a reverse proxy and implement robust HTTP authentication to secure the endpoint.


Alternatives to IFM

Projects in the same categories, ordered by health score.