Exposed .DS_Store file
A macOS .DS_Store file is being served. On its own it only reveals the names of files and folders in that directory — including ones not linked anywhere — which helps an attacker find paths to try. Its real significance is what it implies: this file only reaches production when a whole working directory is deployed ins
Why it matters
A macOS .DS_Store file is being served. On its own it only reveals the names of files and folders in that directory — including ones not linked anywhere — which helps an attacker find paths to try. Its real significance is what it implies: this file only reaches production when a whole working directory is deployed instead of build output, so other private files are likely exposed too.
How ShipReady detects it
Finds files and endpoints that are reachable but should not be. Probes a fixed set of well-known paths — version control directories, environment files, build configuration, debug routes — and derives others from the page's own bundles, such as a source map alongside each script. Every result is gated on content, not status. Many single-page apps answer 200 for every unknown path by serving their index shell, so a 200 alone proves nothing: a source map must parse as one, a directory listing must carry the index signature. Without that gate this check would report an entire class of SPA as catastrophically exposed.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.2.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
A macOS .DS_Store file is being served, revealing directory contents and indicating that a working directory was deployed rather than build output. Delete it from the deployment, add `.DS_Store` to .gitignore and your deploy ignore list, and change your pipeline to publish only build artifacts. Then re-check for other files that shouldn't be public (dotfiles, backups, config).
Frequently asked questions
- What does "Exposed .DS_Store file" mean?
- A macOS .DS_Store file is being served. On its own it only reveals the names of files and folders in that directory — including ones not linked anywhere — which helps an attacker find paths to try. Its real significance is what it implies: this file only reaches production when a whole working directory is deployed ins
- How serious is it?
- ShipReady rates this low. Worth fixing. Small individually, and they accumulate.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site