qkqpttgf/onemanager-php

An index & manager of Onedrive based on serverless. Can be deployed to Vercel/Heroku/SCF/FG/FC/CFC/PHP web hosting/VPS.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 18th, 2026
Created on December 30th, 2019
Open Issues & Pull Requests: 12 (+0)
GitHub issues: Enabled
Number of forks: 2,511
Total Stargazers: 3,798 (+0)
Total Subscribers: 41 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.1 hours
Mean response time: 2.0 days
90th percentile: 7.0 days
Tracked items: 22

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,445 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (2)
  • attention (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

onemanager-php is a serverless application that indexes and manages OneDrive storage through a web interface.

The tool solves the problem of accessing and organizing OneDrive files without building a custom application from scratch. It works by connecting to OneDrive accounts and presenting their contents through a browsable web interface with management capabilities. The application is designed to run on serverless platforms, which means it requires no dedicated server infrastructure to operate.

The tool suits developers and users who want to expose OneDrive storage as a web-accessible file manager without maintaining traditional hosting. It is particularly valuable for those already using serverless infrastructure or cloud platforms, as it can deploy to multiple environments including Vercel, Heroku, Tencent SCF, Alibaba FC, Baidu CFC, Huawei Cloud FG, and standard PHP web hosting or VPS. The flexibility across deployment targets means you can choose based on your existing infrastructure preferences rather than being locked into a single platform.

Development activity shows consistent engagement with the codebase through regular updates and refinements. The project maintains active responsiveness to issues and pull requests, indicating the maintainers are present and addressing user concerns. Code changes span both core functionality and deployment-specific adaptations, reflecting ongoing work to support the multiple platform targets. The repository demonstrates sustained attention to keeping the tool functional across its supported environments.