Skip to content

Classify and remediate cargo-audit findings #8

@mdheller

Description

@mdheller

Summary

TurtleTerm PR #3 currently has Security Checks red only because cargo audit fails. Wrapper safety checks are green.

Current confirmed state on PR #3 head 06390c6202b8e9b708d102e3e1ab5eb7275b95aa:

Green:

  • Trust Surface
  • Wrapper safety checks
  • Script Checks
  • verify-pages

Still red:

  • Security Checks: cargo audit

Why this likely needs separate handling

PR #3 adds docs, a Python receipt-context smoke test, and packaging/verification remediation. It does not intentionally change Rust dependencies. Cargo audit findings are therefore likely repo-wide dependency/security posture rather than CloudShell FOG integration semantics.

Acceptance criteria

  • Capture exact cargo-audit advisories.
  • Decide whether to update dependencies, add justified ignores, or split advisories into separate remediation issues.
  • Security Checks pass or have explicit documented exception policy.

Related

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions