Homepage

@axonflow/openclaw@1.2.0

Connects to AxonFlow (SaaS or self-hosted) for policy enforcement, PII scanning, approval gates, and audit trails in OpenClaw agents

  • latest version

    2.8.5

  • latest non vulnerable version

    2.8.5

  • first published

    4 months ago

  • latest version published

    17 days ago

  • licenses detected

  • View openclaw package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @axonflow/openclaw package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Incorrect Permission Assignment for Critical Resource

    @axonflow/openclaw is a Policy enforcement, approval gates, and audit trails for OpenClaw — govern tool inputs before execution, scan outbound messages for PII/secrets, and record agent activity for review and compliance

    Affected versions of this package are vulnerable to Incorrect Permission Assignment for Critical Resource due to improper permission settings on directories and credential files. An attacker can access sensitive registration credentials and cache state by reading files in ~/.config/axonflow/ and ~/.cache/axonflow/ if the user's home directory or configuration directories are set to permissive modes. This is only exploitable if the user's home or configuration directories are world-readable or group-readable.

    How to fix Incorrect Permission Assignment for Critical Resource?

    Upgrade @axonflow/openclaw to version 2.0.0 or higher.

    <2.0.0
    Go back to all versions of this package