Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Srednoff Installed Dependency Advisory Exposure Reviewer

    1

    Produce a revision-bound lockfile/SBOM-to-advisory applicability ledger with direct/transitive paths, reachability evidence, remediation priorities and explicit coverage gaps; not a live CVE scanner.

    $7.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Srednoff Installed Dependency Advisory Exposure Reviewer

    Example session with this skill installed

    Triage this release lockfile against supplied dated advisories without installing anything.

    • Read your context and instructions
    • Compiled the srednoff installed dependency

    Expected report shape, not a completed real audit: Executive Summary; Scope; Assets / Trust Boundaries

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Srednoff Installed Dependency Advisory Exposure Reviewer

    One-Line Outcome

    Produce a revision-bound lockfile/SBOM-to-advisory applicability ledger with direct/transitive paths, reachability evidence, remediation priorities and explicit coverage gaps; not a live CVE scanner.

    Short Description

    Manifest ranges, duplicated advisory aliases and incomplete deployment evidence can inflate or hide exposure; candidate-library due diligence does not establish what an installed release contains.

    Problem It Solves

    Manifest ranges, duplicated advisory aliases and incomplete deployment evidence can inflate or hide exposure; candidate-library due diligence does not establish what an installed release contains.

    Application security owner: pinned lockfile/SBOM-to-advisory inventory, affected-version and reachability evidence ledger, triaged remediation priorities and unresolved coverage.

    What You Get

    • Executive Summary
    • Scope
    • Assets / Trust Boundaries
    • Evidence Reviewed
    • Resolved Dependency And Introduction Graph
    • Advisory Alias And Applicability Ledger
    • Findings
    • Critical Findings
    • Quick Wins
    • Prioritized Remediation Plan
    • Missing Evidence
    • Residual Risk
    • Verification Checklist

    How It Works

    1. Bind inventory and advisory collection to the candidate revision/time; separate lockfile resolution, built contents and deployed runtime as three evidence layers.
    2. Read the supplied structured format using established parsers where permitted; never install dependencies, execute lifecycle scripts or fetch private graphs merely to inspect them.
    3. Normalize package identity by ecosystem, namespace/name, exact resolved version or source commit and integrity/source metadata. Keep multiple installed versions as separate nodes.
    4. Trace direct and transitive introduction paths, optional/platform branches and production versus development scopes; a build-only dependency can still affect build integrity and is not automatically irrelevant.
    5. Match primary advisories by actual package identity and ecosystem-aware affected-range semantics. Do not compare versions lexically or apply SemVer rules to a different ecosystem or Git range.
    6. Reconcile CVE/GHSA/OSV aliases into distinct issue records while retaining each source and modification date. Preserve withdrawn, disputed, conflicting and unmapped records rather than silently counting them as current confirmed defects.
    7. Classify version applicability separately from reachability and deployment presence: AFFECTED_VERSION, NOT_IN_STATED_RANGE or UNKNOWN for version; SUPPORTED, NOT_DEMONSTRATED or UNKNOWN for exposure evidence. These are local report labels, not exploit guarantees.
    8. Inspect supplied call sites, feature flags, configuration, attack preconditions and vendor backport evidence. A patched source build may differ from its nominal version; require provenance before dismissing a range match.
    9. Review installed-package origin and suspicious name/source changes, unexpected install permissions and unsupported maintenance as separate supply-chain concerns; do not label typosquatting or malware from resemblance alone.
    10. Prioritize by supported impact, attack path, exposed privileges and change cost. Retain source severity separately from contextual urgency and confidence; no fabricated CVE/CWE or universal upgrade threshold.
    11. Recommend evidence collection, tested mitigation or an exact candidate fix version only when supported by the advisory and compatibility evidence. Hand selected migration work to concept66; do not execute updates or resell core40 candidate selection.
    12. Deliver the reconciled inventory, advisory ledger, unsupported/unknown coverage and owner action plan with retest criteria for a new revision. A clean database result is not proof of no vulnerabilities.

    Best For

    Application security owners triaging the resolved dependency graph of a specific release

    Example Tasks

    • Triage this release lockfile against supplied dated advisories without installing anything.
    • Reconcile duplicate advisory aliases and unknown runtime reachability.

    Inputs

    • Release revision, manifests and lockfiles or SBOM with format/tool version, ecosystem, collection time and permitted evidence scope.
    • Build/deployment identity and production/development/optional dependency boundaries, including platform selection where supplied.
    • Dated primary advisory snapshots or approved public source links with package identity, affected/fixed ranges, aliases and withdrawal status.
    • Sanitized call-path, configuration and runtime evidence for applicability; missing reachability remains unknown.

    Outputs

    • Executive Summary
    • Scope
    • Assets / Trust Boundaries
    • Evidence Reviewed
    • Resolved Dependency And Introduction Graph
    • Advisory Alias And Applicability Ledger
    • Findings
    • Critical Findings
    • Quick Wins
    • Prioritized Remediation Plan
    • Missing Evidence
    • Residual Risk
    • Verification Checklist

    Permissions

    Read-only review of owner-supplied artifacts by default. Report file writes, shell/local fixture execution and official documentation lookup are optional, require available tools and their explicit scope. No live credentials are requested.

    Compatibility

    Standalone workflow, no Srednoff OS dependency. Codex evidence is synthetic entrypoint text only when recorded below. Claude Code, Cursor and actual buyer-runtime task delivery remain UNTESTED. Provider/platform-specific contracts must be refreshed for the installed version.

    Limitations

    This is an instruction/evidence workflow, not a hosted security service, persistent enforcement engine, production certification or business guarantee. The optional Python helper checks supplied claims, not underlying source artifacts. Agensi delivery is agent-only: do not save/export proprietary skill files to run local helpers; disclose NOT_EXECUTED where execution is unavailable.

    Validation Transparency

    Offline evidence-precheck status: PASS. Authored synthetic text-response cases: 16/16, status PASS. This is not independent security testing, complete artifact inspection or proof of deployment safety. Exact-text hashes and attempts are retained separately.

    License And Publisher

    Commercial License 1.0 covers original new expression; historical MIT and third-party rights remain unchanged. Mandatory marketplace conditions prevail. Publisher: Ivan Srednoff / Srednoff.Agency. No proprietary source resale or off-platform paid upsell is included.

    FAQ

    What is different from a generic security request? Application security owner: pinned lockfile/SBOM-to-advisory inventory, affected-version and reachability evidence ledger, triaged remediation priorities and unresolved coverage. No generic package recommendation, continuous CVE feed/scanner claim, license audit or upgrade migration implementation.

    Does it change production automatically? No. Audit/design is the default; changes, secret rotation, IAM, network probes and financial actions need separate explicit authorization.

    Are the examples real incidents? No. They are synthetic DEMO DATA.

    Is this a certification or guaranteed protection? No. Evidence gaps, residual risk and unexecuted tests remain explicit.

    Can I use project-specific reports for clients? Yes under the included license; proprietary workflow source is not a client deliverable.

    Version

    1.0.0

    Release Notes

    Initial scoped security workflow with domain decision rules, evidence requirements, synthetic examples, regression cases and explicit authorization/runtime limits. No production/customer outcome is claimed.

    This is an instruction/evidence workflow, not a hosted security service, persistent enforcement engine, production certification or business guarantee. The optional Python helper checks supplied claims, not underlying source artifacts. Agensi delivery is agent-only: do not save/export proprietary skill files to run local helpers; disclose NOT_EXECUTED where execution is unavailable.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Permissions

    Terminal / Shell
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    Produce a revision-bound lockfile/SBOM-to-advisory applicability ledger with direct/transitive paths, reachability evidence, remediation priorities and explicit coverage gaps; not a live CVE scanner.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Srednoff Installed Dependency Advisory Exposure Reviewer on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Security