larksuite/cli lark-okr
Checked the catalogued skill at lark-okr.
A set by no findings on this axis
D; retained sample includes a high finding · SD-003 · what this rule accepts as a false positive →
A set by no findings on this axis
47 suppressed by AI triage
The reference uses a relative path for a markdown link within the skill manifest, not for code execution.
The reference points to a sibling skill's markdown file via a relative path, which is safe in documentation.
Same as finding 2: a harmless markdown link to another skill.
Same as finding 2: a harmless markdown link to another skill.
The path reference is in documentation (a Markdown link) and is not used by code, so it does not pose a traversal risk.
The referenced path appears only in a markdown link within documentation and is not executed or accessed by the skill code.
Link to another markdown file uses relative path, no file access.
Same as above, a documentation link, not a file operation.
Documentation reference to a relative path, not executable code.
Documentation reference to a relative path, not executable code.
Documentation file contains relative path references, not executable code performing traversal.
Documentation file lists relative links; no active path traversal occurs.
Link uses a relative path in documentation, not executable code.
Reference link in markdown documentation; no code execution risk.
Documentation link using a relative path; no code execution possible.
Documentation link using a relative path; no code execution possible.
The link is a relative reference in documentation, not executable code.
The link is a relative reference in documentation, not executable code.
The link is a harmless relative reference within documentation.
The reference uses ../ in a documentation file and does not enable arbitrary file access.
Documentation uses a relative path; not executable code.
Documentation contains a relative reference; safe.
Relative path reference in documentation, not executable code.
Documentation listing relative path to shared skill, safe context.
The path reference appears in documentation and is not executed.
The relative path in documentation is harmless and not used to read or write files.
Relative documentation link, no code execution or file access.
Relative markdown link in documentation, not a security vulnerability.
Documentation may include example paths; no executable code present.
Relative path within repository documentation, not a system file access
Relative path within repository documentation, not a system file access
The file is documentation and only contains relative links, not executable code.
The file is documentation and only contains relative links, not executable code.
The referenced path is a documentation link, not runtime code that traverses the filesystem.
The path appears only in a documentation reference, not executed code, thus not a threat.
The relative path is used only in documentation, not executed code.
The relative link appears only in documentation, not executable.
Relative path reference in documentation, no executable code involved.
Relative path reference in documentation, not used for code execution.
The file is documentation; the path traversal is only a markdown link to another doc, not executable code.
The path traversal appears only in a reference link within a markdown file, posing no real threat.
The relative path is only a documentation link, not executable code, so it poses no real threat.
The path appears only in a documentation reference, not executed code, thus not a threat.
Only a documentation reference to a relative path; no code execution.
Only a documentation reference to a relative path; no code execution.
The path is in a markdown link, not executable code, so no actual file access occurs.
The path appears only as a documentation link, not as code that would be executed.