Credential access
Reads Dropbox tokens, config, and selected local files.
brew
Install dropbox-uploader with Homebrew
Bash script for interacting with Dropbox. Version 1.0 via Homebrew; verified from local package data.
agent safety
Agent safety answer
dropbox-uploader transfers files to and from Dropbox using local credentials.
Remote mutation
Can upload, delete, move, and overwrite Dropbox content.
Publish/artifact risk
Can publish or remove artifacts in shared storage.
Recommended control
Gate uploads, deletes, moves, and token reads.
Agent-use guidance
Allow listing; require approval for transfers, deletes, and sensitive file paths.
install
Additional install commands
macOS
Homebrewverified · 100%
brew install dropbox-uploaderlocal Homebrew formula metadata
overview
Package summary
Bash script for interacting with Dropbox
Project links
Commands and aliases
- dropShell.sh
- dropbox_uploader.sh
history
Project history and usage
Dropbox Uploader is a Bash-and-cURL command-line script for uploading, downloading, listing, sharing, monitoring, and otherwise managing Dropbox files from a shell. Its package-manager appeal is that it turns Dropbox access into one portable script rather than a desktop sync client or heavier SDK application.
Project history
The project grew around a simple Unix idea: use a shell script plus cURL to talk to Dropbox from systems where a GUI client is unavailable or inappropriate. Its README now documents Dropbox API v2 authentication, a first-run configuration wizard, and storage of access configuration in `~/.dropbox_uploader`.
Adoption history
Dropbox Uploader found a niche with headless machines, NAS boxes, backup scripts, Raspberry Pi setups, and cross-platform shells. The official tested-environment list includes GNU/Linux, FreeBSD, macOS, Windows/Cygwin, and Raspberry Pi, which explains why a Homebrew package remains useful even though the tool is only a script.
How it is used
Common usage is automation-friendly file transfer: upload backups, download artifacts, list remote folders, create share links, monitor remote paths for changes, and unlink credentials. The first run guides the user through OAuth-style setup without storing the Dropbox account password.
Why package nerds care
For package nerds, Dropbox Uploader is a classic single-script utility: no daemon, no GUI, no SDK install, just Bash, cURL, and a config file. It matters because it preserves a scriptable Dropbox workflow for environments where official desktop sync is the wrong shape.
Timeline
- 2010s: Dropbox Uploader becomes a popular shell-script interface to Dropbox.
- Later: The project moves to Dropbox API v2 authentication and documents a first-run configuration wizard.
- README era: The README points users to the GitHub wiki for tips and contributed examples.
Related projects
- Dropbox itself provides the storage and API surface.
- cURL is the only required command-line dependency called out by the project.
- The project's GitHub wiki collects examples and usage tips around the script.
Sources
security posture
Risk level: yellow
broad file, network, media, or database tool signal. generalized runtime or code generation signal.
Risk classifier
yellow risk · medium confidence · runtime
Why
- broad file, network, media, or database tool signal
- generalized runtime or code generation signal
Signals
- text:shell
- text:upload
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- Homebrew bottle metadata is available for 1 platform targets.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
~/.dropbox_uploader
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.dropbox_uploader
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
dropShell.sh | cli | global executable | |
dropbox_uploader.sh | cli | global executable |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-07-10
manager version1.0
manager updated
local dataok
upstreamcurrent
latest detected1.0
https://github.com/andreafabrizi/Dropbox-Uploader
- infoNo package-manager update timestamp was available.low confidence
install metadata
Package metadata
| Package key | brew:dropbox-uploader |
|---|---|
| Version | 1.0 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/dropbox-uploader |
| Homepage | https://www.andreafabrizi.it/2016/01/01/Dropbox-Uploader/ |
| Repository | https://github.com/andreafabrizi/Dropbox-Uploader |
| Upstream docs | https://github.com/andreafabrizi/Dropbox-Uploader#readme |
| License | GPL-3.0-or-later |
| Source archive | https://github.com/andreafabrizi/Dropbox-Uploader/archive/refs/tags/1.0.tar.gz |
| Bottle | available (on all) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
Source database details
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | dropbox-uploader |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated agent safety answer
- curated configuration and credential file locations
- curated package history
- package relationship graph
- package version freshness
- package-page enrichment