Scanned skills

nvidia/skills deepstream-sop

Checked the catalogued skill at deepstream-sop.

SkillTrust corpus scan 3 October 2026 v0.13.0 via skillsh Verify on GitHub
D AI-triaged 170
D Security

D; retained sample includes a high finding · SD-007 · what this rule accepts as a false positive →

D Permissions

D; retained sample includes a high finding · SD-003 · what this rule accepts as a false positive →

B Transparency

B set by findings not listed in the stored summary

showing 10 of 170
securityhigh SD-007
SKILL.md
permission_hygienehigh SD-003
configs/nvds_preprocess_template.txt
securityhigh SD-007
references/Dockerfile_reference
securityhigh SD-007
references/Dockerfile_reference
securityhigh SD-007
references/Dockerfile_reference
securityhigh SD-007
references/Dockerfile_reference
permission_hygienehigh SD-003
references/Dockerfile_reference
securityhigh SD-007
references/Dockerfile_reference
permission_hygienehigh SD-003
references/Dockerfile_reference
securityhigh SD-007
references/Dockerfile_reference
18 suppressed by AI triage
securityhigh SD-007 benign_example
evals/evals.json

The file contains a test example with a curl or Python request snippet, not an actual outbound call.

securityhigh SD-007 benign_example
evals/evals.json

Same as above; the content is a benign example of an outbound request pattern.

securityhigh SD-007 benign_example
references/Makefile_custom_postprocess_reference

The URL appears only in a comment referencing the license, not as an executable network request.

permission_hygienehigh SD-003 benign_example
references/Makefile_custom_postprocess_reference

The relative include path is used for compilation, not for runtime file access outside the skill.

permission_hygienehigh SD-003 benign_example
references/Makefile_custom_postprocess_reference

Absolute system include path is part of build configuration, not a runtime traversal.

permission_hygienehigh SD-003 benign_example
references/Makefile_custom_postprocess_reference

Relative include path is a standard compile-time reference, not a malicious traversal.

securityhigh SD-007 benign_example
references/copy_sources_reference.sh

The URL appears only in a comment, not in executable code.

securityhigh SD-007 benign_example
references/ddm_net_reference.py

The URL is a license reference in a comment, not an executable network call.

securityhigh SD-007 benign_example
references/export_ddm_to_tensorrt_reference.py

The URL is in a license comment, not an actual outbound call.

permission_hygienehigh SD-003 benign_example
references/export_ddm_to_tensorrt_reference.py

Hardcoded absolute path is not user‑controlled, so no path traversal risk.

permission_hygienehigh SD-003 benign_example
references/export_ddm_to_tensorrt_reference.py

Hardcoded absolute path is safe; it is not derived from external input.

securityhigh SD-007 benign_example
references/messager_reference.py

The URL is only in a comment/header, not executed as a network call.

securityhigh SD-007 benign_example
references/messager_reference.py

The URL appears only in a comment, not as an executable network request.

securityhigh SD-007 benign_example
references/missing_number_detector_reference.py

The URL is only in a comment/header, not executed as a network call.

securityhigh SD-007 benign_example
references/protos_init_reference.py

The URL is a static license reference in a comment, not an executed network request.

permission_hygienehigh SD-003 benign_example
references/skill_01_fastapi_endpoints.md

No path traversal or absolute system directory paths found in the file content.

permission_hygienehigh SD-003 benign_example
references/skill_05_triton_ddm_model.md

The file is a Markdown documentation containing example code; the path traversal occurs only in a code snippet, not executed, so it is not a real threat.

securityhigh SD-007 benign_example
references/vllm_inference_reference.py

The URL appears only in a comment referencing the license, not as an executable network request.