wsgidav
4.3.1 open-sourceThe section your link pointed to isn't on wsgidav's page any more, so we've brought you to the top.
WsgiDAV is a generic and extendable WebDAV server written in Python and based on WSGI.
fs_dav_provider:
follow_symlinks: true
fs_dav_provider:
shadow_map: '/path/to/favicon.ico'
wsgidav --server=uvicorn
lock_storage:
class: my_custom_lock.LockStorage
args: []
kwargs:
path: "/data/locks"
wsgidav --server=gevent
wsgidav --config wsgidav.json --root '~/shares/data'
wsgidav --server=cheroot --ssl-adapter=pyopenssl
wsgidav --cherrypy-wsgiserver
hostname = 'localhost'
Port = 8080
[webdav]
[dir_browser]
msSharepointUrls = True
add_header_MS_Author_Via = True
Summary
wsgidav is an open-source WebDAV server, written in Python on WSGI, that turns a directory tree into a network share reachable over HTTP with optional SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. and authentication. It installs via pip and runs as a command-line script on Linux, macOS, or Windows, with options like --auth and --browse for quick setup or a config file for domain controllers such as PAMPAMBrokering administrator sessions through a gateway instead of handing out standing credentials. Access is granted for one session, to one target, and recorded., htpasswd, or htdigest. It suits developers and system administrators who need a lightweight, scriptable file-sharing endpoint rather than a full NAS appliance or cloud storage service. Recent changelog entries note fixes for CVEs in an example MySQL provider and symlink handling, worth checking before deployment. First committed in 2009, it remains active with 56 contributors, dozens of yearly commits, and a release only 55 days old.
WsgiDAV is a generic and extendable WebDAV server written in Python and based on WSGI.
How wsgidav helps
How do I let a team drop files into a shared folder without setting up a file server appliance?
it turns any directory on the machine into a WebDAV share reachable over plain HTTP or HTTPS, so any WebDAV-capable client can mount it directly
Which folder on this machine is exposed to the network and is it writable by anyone?
the startup log lists each registered share by route and filesystem path along with whether it is read-only or read-write, and warns explicitly when anonymous write access is allowed
Who is allowed to authenticate against this share, and against what existing accounts?
a domain controller setting binds logins to PAM, an Apache htpasswd file, or an htdigest file instead of a separate user database, so access follows accounts that already exist
Is this share's traffic, including credentials, exposed on an untrusted network?
it warns at startup when basic authentication is active without SSL enabled, flagging the exact condition under which passwords would travel in the clear
Am I running a version with a known security hole in the pieces I actually enabled?
the changelog names fixed CVEs by version and clarifies that some, like the MySQL provider injection, only apply to installations that explicitly turned that example module on
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for wsgidav, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail wsgidav puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
21 entries
No entries match these filters.
- June 20262
- May 20261
- March 20241
- September 20231
- February 20231
- November 20222
- January 20221
- January 20211
- March 20191
- May 20181
- April 20181
- February 20171
- November 20161
- October 20161
- August 20161
- May 20151
- August 20143
Project health
Issue, contributor and maintainer activity in mar10/wsgidav, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 6 +2 vs prior 12 months
- Maintainers 2 +2 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 88% of issues opened, last 12 months
- Median time to close 20 days first maintainer reply 4.5 days
- Open backlog 3 of 205 issues ever filed
- Issues opened / month 2 · 0 communitymaintainers
- Open backlog 3
- Contributors / month 2
- Commits / month 17
- Stars 1,233
- bugs 75%
- features 25%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.