exasol-bucketfs — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited exasol-bucketfs (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
BucketFS is Exasol's synchronous distributed file system: whatever is written to a bucket is replicated to every cluster node and mounted read-only inside UDFs at /buckets/<service>/<bucket>/<path>. Replication takes time, and recognised archives are extracted on top of it, so a fresh upload becomes usable only once synchronisation finishes. This skill covers moving files in and out of BucketFS and referencing them from scripts.
Choose the narrowest matching route. If several apply, load all matching references before answering.
exapump bucketfs, ls, cp, rm, upload, download, delete, --bfs-host, --bfs-bucket, bfs_write_password, config.toml, exapump profile addreferences/exapump-bucketfs-cli.mdupload jar, %jar, upload model, load model in UDF, upload SLC, activate containerreferences/bucketfs-udf-usage.mdwhat is BucketFS, bfsdefault, service, bucket structure, replication, backup, atomic write, size limitreferences/bucketfs-concepts.mdAn upload for a UDF usually needs routes 1 and 2 together: the command form comes from the CLI reference, the path spelling in the SQL from the usage reference.
Ensure a working exapump profile — BucketFS uses the profile's bfs_* fields — before running any command:
exapump bucketfs ls --profile <name>; always place --profile after the subcommand. Otherwise test the default profile with exapump bucketfs ls.--profile <name> after the subcommand on every later command, such as exapump bucketfs cp --profile <name> <local-file> <bucket-path>.exapump profile list to see which profiles exist.exapump profile show <name> — it masks credentials — to confirm the required fields are set. Never read, `cat`, or print `~/.exapump/config.toml`; it stores credentials in clear text. If a credential value does appear in any command output, do not repeat it in the conversation.exapump profile add <name> (omit --password and exapump prompts on a hidden line) or exapump profile init, then retry step 1. Never ask the user to paste a password into the conversation, and never pass one as a command-line argument.rm, show the exact bucket, path, and profile, then obtain explicitconfirmation. BucketFS is not part of database backups, so a deletion is not recoverable from a database restore.
cp that would overwrite an existing BucketFS or local file, inspectthe target and obtain confirmation.
profile can hold them securely. Inspect a profile with exapump profile show <name>, never by reading ~/.exapump/config.toml.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.