This free page contains the context needed to interpret the published static score. Deep review and runtime validation are separate evidence levels, not hidden score modifiers or certifications.
The pinned smolagents snapshot scored 81 under the static AI baseline. All four required evidence providers completed with no unexpected scope gaps; the result describes repository-visible posture and does not test runtime behavior.
All four required static evidence providers completed successfully.
No unexpected static controls were left unassessed, and repository evidence supported the assessed agentic, data-exposure, observability, and evidence-readiness controls.
Evidence-backed weaknesses
Two references in the test workflow use mutable GitHub Actions version tags rather than immutable full commit SHAs.
The repository-posture dimension scored 44, lower than its other static dimensions in this snapshot.
Limits and next action
Twelve expected controls outside static reach—including prompt injection, authorization, isolation, exfiltration, and resource-limit behavior—were not assessed.
A generated lockfile finding was suppressed during editorial adjudication because a reusable Python library is not necessarily expected to commit an application lockfile.
Documentation, configuration, and code markers are not proof that controls remain effective in a deployed runtime.
Editorial adjudication was AI-assisted project-owner review, not independent certification or human ground truth.
Remediation guidance
Pin third-party GitHub Actions to reviewed full commit SHAs while retaining readable release tags in comments.
Use selective runtime testing to evaluate prompt-injection resistance, tool authorization, secret isolation, exfiltration boundaries, output handling, resource limits, and security telemetry.
No reviewed public case file is attached.
Public-safe finding summaries
medium
Build workflow dependencies use mutable references
The test workflow references actions/checkout@v6.0.3 and actions/setup-python@v6 rather than immutable full commit SHAs. This is a static build-integrity weakness, not evidence of compromise.