Scan Probe (temporary)
Purpose
This package is a throwaway measurement instrument. The registry's static analysis engine runs server-side and is not distributed with the CLI, so its rule set cannot be inspected locally. Rather than guessing which Python patterns are reported, this probe publishes one isolated pattern per file and reads the resulting report. The package is deleted immediately afterwards.
The four probes are deliberately separated so that every finding can be mapped to exactly one language construct:
| File | Construct under test |
|---|---|
probe_subprocess.py |
subprocess.run with an absolute-path argument vector and no shell |
probe_ctypes.py |
ctypes.WinDLL call into a system library |
probe_osopen.py |
atomic owner-only file creation via os.open(..., 0o600) |
probe_chmod.py |
POSIX owner-only directory mode via os.chmod(..., 0o700) |
Why the answer matters
The real skill stores conversation archives on local disk. Hardening that storage requires either spawning a platform tool or calling a platform API, and the choice determines whether the published artifact stays free of any external command execution. The probe therefore decides an architectural question, not a cosmetic one.
Scope and safety
- Nothing here is executed, imported, or referenced by any other package.
- No file reads, no network access, no credential access, no persistence.
- No behaviour is triggered by installing or reading this package.
- The probe is removed as soon as the report has been downloaded.
Removal
After the report is retrieved the package is withdrawn with the registry's own delete command, so it does not remain visible in the publisher's catalog.