aws/agent-toolkit-for-aws amazon-keyspaces
Checked the catalogued skill at amazon-keyspaces.
C; retained sample includes a medium finding · SD-008 · what this rule accepts as a false positive →
A set by no findings on this axis
A set by no findings on this axis
43 suppressed by AI triage
Hardcoded /tmp output path used only for temporary data, not user-controlled or reading files, so no real threat.
Hardcoded /tmp directory for temporary output; no arbitrary file access, so benign.
Hardcoded /tmp path used for output only, not allowing arbitrary file traversal, so benign.
Uses /tmp for temporary JSON output; not a real threat.
Hardcoded /tmp path for output; safe.
Writes to /tmp for temporary data, not dangerous.
Hardcoded /tmp output for PDF generation; benign.
Documentation shows static host configuration, not dynamic DNS exfiltration.
Example curl command downloads certificates, not an outbound exfiltration activity.
Example command writes to /tmp; harmless absolute path.
Same example output; harmless absolute path.
The documented table entry does not involve any DNS query or tunneling; the flagged phrase is a false positive.
The path /tmp/keyspaces-calc.json is a standard temporary output location in documentation, not an attack.
The absolute path in the command is a normal temporary file used in documentation, not a malicious path traversal.
Example documentation referencing /tmp path; not executed.
Example documentation referencing /tmp path; not executed.
Example documentation referencing /tmp path; not executed.
Example documentation referencing /tmp path; not executed.
Example documentation referencing /tmp path; not executed.
The file is documentation showing example usage, not executable code that would write to /tmp.
Example comment in documentation; no actual file operations performed by the system.
Same as above—commented example, not active code.
Documentation of a script invocation; absolute paths are placeholders, no direct system access.
Same as previous—documentation example, not executed automatically.
Documentation comment; no code runs that would write to [REDACTED]
Documentation example of output path; not a real path traversal threat in this context.
Documentation shows example usage with absolute paths, not actual execution.
Documentation example, no threat.
Example command in docs, safe.
Illustrative path usage in documentation.
Example usage, benign.
Documentation path reference.
Doc example of output path.
Illustrative command in docs, not active code.
The file is documentation describing credential handling; no evidence of code accessing secrets.
Documentation context, no code that reads credentials is present.
The content is explanatory, not executable, and does not involve credential access.
The absolute path references appear only in documentation comments showing example usage, not in executable code.
The path is shown as a command‑line example in a comment, not as code that will access the filesystem.
This reference is part of an example invocation in comments, not actual code logic.
The path is included only in a documentation comment, not in executable statements.
The output path is shown in a comment example, not used directly by the script.
The path traversal references a project asset folder relative to the tsconfig and does not expose system files; it is benign.