modelstudioai/skills › bailian-docs-llm-wiki

Documentation example illustrating outbound network call permission, not an active threat

The text is a documentation note describing a logged outbound call, not an executable network request.

The file is documentation, not executable code, and merely references a potential outbound network call scenario.

The file is documentation, not executable code, and merely references a potential outbound network call scenario.

The file is documentation describing outbound network call patterns, not an executed call or configuration enabling such calls.

Same reasoning: documentation example, not a threat.

File is prose; outbound call patterns are mentioned as examples, not real network calls.

Same reasoning: documentation example, not a threat.

The file is documentation prose that references base64 usage, not malicious code execution.

Only empty lines present; no evidence of Base64 usage.

Documentation file, no executable code or real base64 data found.

Documentation placeholder, not actual code.

Documentation file, no executable code or real base64 data found.

Documentation file, no executable code or real base64 data found.

No evidence of base64 obfuscation present in the context lines.

Documentation placeholder, not actual code.

Documentation placeholder, not actual code.

Documentation placeholder, not actual code.

Documentation placeholder, not actual code.

Documentation placeholder, not actual code.

Documentation placeholder, not actual code.

Documentation placeholder, not actual code.

No base64-encoded data present; the scanner likely flagged an empty or placeholder line.

No base64-encoded data present; the scanner likely flagged an empty or placeholder line.

No base64-encoded data present; the scanner likely flagged an empty or placeholder line.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation and the outbound call is an example, not executable code.

The file is documentation with no actual base64 payload or execution context, so the flag is a false positive.

The line contains documentation text, not executable code or configuration that would perform outbound network calls.

Documentation context for outbound calls.

Placeholder config file with no actual outbound network call.

The outbound network call is shown as a code example in documentation, not an active network request.

Only whitespace is present; no malicious Base64 usage detected.

No Base64 strings or decoding commands are present.

The content is documentation text, not executable code or configuration that would perform outbound network calls.

Outbound network call patterns are described in documentation, not active code.

The file is documentation with no actual base64 payload or execution context, so the flag is a false positive.

Documentation describing outbound network call patterns, not an executable configuration or code

The file is documentation with no actual base64 payload or execution context, so the flag is a false positive.

Documentation file contains illustrative text, not executable code, so path traversal references are benign examples.

The line contains documentation text, not executable code or configuration that would perform outbound network calls.

The matched line appears to be a documentation note describing an outbound network call rather than an actual configuration or code that enables such a call.

The line contains documentation text, not executable code or configuration that would perform outbound network calls.

Documentation merely references outbound network call patterns, not executing or configuring them.

Documentation describing configuration that permits outbound calls, not malicious code.

Documentation config example, not an active outbound call.

The file is documentation and contains only a comment about detecting outbound calls, not actual code or configuration that performs a network call.

Documentation config example, not an active outbound call.

The file contains only a placeholder text about outbound network calls, not an actual call or permission grant.

The flagged text is a documentation note, not executable code or configuration that initiates an outbound network call.

File is prose; outbound call patterns are mentioned as examples, not real network calls.

Descriptive reference to outbound network capability.

The file is documentation, not executable code; the referenced outbound call is only noted in prose and not an actual configuration.

The file is a documentation text with no executable code or config that would enable outbound network calls.

Only a textual reference in documentation, no executable code or configuration enabling outbound network calls.