sca-blackduck
Assess Dependencies with Black Duck
Dependency vulnerabilities and license risks can reach production unnoticed. This skill guides Black Duck scans, policy gates, SBOM creation, and remediation triage.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "sca-blackduck" from https://skillstore.io/skills/agentsecops-sca-blackduck.md and its manifest at https://skillstore.io/api/skills/agentsecops-sca-blackduck/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "sca-blackduck". Triage one critical library vulnerability with a fixed version.
Expected outcome:
- Priority: Immediate because the vulnerable component is deployed and a supported fixed version exists.
- Action: Upgrade in a test branch, run compatibility tests, and repeat the Black Duck scan.
- Evidence: Record the original finding, fixed version, validation result, owner, and completion date.
Using "sca-blackduck". Review a new copyleft license finding.
Expected outcome:
- Classify the license obligations and confirm whether distribution triggers them.
- Ask legal counsel to review product use, linking method, and planned distribution.
- Replace the component or document a time-limited approved exception.
Using "sca-blackduck". Define a pull request dependency gate.
Expected outcome:
Run on relevant dependency changes, block approved severity violations, retain reports, and fail when scan status is unavailable.
Security Audit
CriticalMost static alerts are false positives caused by Markdown examples, reference URLs, configuration exclusions, and legitimate environment access. Confirmed findings involve unverified remote scripts executed by CI templates and user instructions. Additional review found mutable GitHub Action tags, unsafe Jenkins interpolation, and a pull request comment that reports fixed zero findings.
Confirmed security concerns (5)
Capability review items (13)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
๐ Filesystem access (6)
โ๏ธ External commands (50)
๐ Network access (50)
๐ Env variables (37)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/agentsecops-sca-blackduck/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/agentsecops-sca-blackduck?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/agentsecops-sca-blackduck?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentsecops-sca-blackduck/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/agentsecops-sca-blackduck.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
AgentSecOps. (2026). sca-blackduck security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/agentsecops-sca-blackduck/audits/9BibTeX citation
@techreport{agentsecops-agentsecops-sca-blackduck-2026,
author = {AgentSecOps},
title = {sca-blackduck security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/agentsecops-sca-blackduck/audits/9},
note = {Author version 0.1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "sca-blackduck security audit report (audit version 9)"
version: "0.1.0"
type: report
authors:
- name: "AgentSecOps"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/agentsecops-sca-blackduck/audits/9"
identifiers:
- type: other
value: "skillstore:agentsecops-sca-blackduck:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Triage dependency vulnerabilities
Prioritize Black Duck findings, map affected components, and recommend upgrades or compensating controls.
Build a CI policy gate
Adapt a pipeline template to scan dependencies, retain reports, and enforce approved severity thresholds.
Review license exposure
Classify dependency licenses, identify policy conflicts, and prepare exceptions for legal review.
Try These Prompts
Identify dependency manifests in [repository]. Propose a Black Duck scan plan with required credentials and expected reports.
Review these Black Duck findings: [findings]. Prioritize remediation by exploitability, component reachability, fixed versions, and business impact.
Design a [CI platform] Black Duck gate for [repository]. Define scan triggers, policy thresholds, artifact retention, and failure behavior.
Assess [dependency portfolio] for dependency confusion, abandoned components, compromised maintainers, license conflicts, and SBOM gaps. Produce a prioritized control plan.
Best Practices
- Store Black Duck tokens in the CI secret store and grant only required permissions.
- Pin and verify every downloaded installer and third-party CI action.
- Repeat scans after dependency changes and record evidence for accepted risks.
Avoid
- Do not execute downloaded scripts without version pinning and integrity verification.
- Do not treat placeholder summaries as evidence of a successful clean scan.
- Do not rely on referenced scripts that are absent from the installed package.
Frequently Asked Questions
Does this skill run Black Duck scans automatically?
Which CI systems are covered?
Can it generate an SBOM?
Does it provide current CVE data?
Can it make legal license decisions?
Are the bundled CI templates production ready?
Developer Details
Author
AgentSecOpsLicense
MIT
Author version
v0.1.0
Skillstore revision
r2
Ref
181fdefcafd96b041926e61c4b2e306ca7e7820e
Maintenance freshness
7/24/2026
Usage
6 downloads ยท 261 views
File structure
๐ assets/
๐ .gitkeep
๐ blackduck_config.yml
๐ ci_integration/
๐ github_actions.yml
๐ gitlab_ci.yml
๐ policy_templates/
๐ security_policy.json
๐ rule-template.yaml
๐ references/
๐ EXAMPLE.md
๐ remediation_strategies.md
๐ SKILL.md