TavernKeeper Scan Report

leandrojofre/SillyTavern-Presence

Commit 0dcab46 Reviewed

No material or immediate-danger concern was identified in this review.

This advisory report describes what the named tools and review process found at one exact commit. Unknown or unobserved behavior may still exist.

0 immediate danger 0 material 5 low

What this review found

No material or immediate-danger item was identified.

Minor cautions

zizmor reported archived-uses

Minor caution · high confidence

The release automation uses an outdated tool that is no longer maintained. While it still works, it will not receive security fixes in the future. This is a maintenance concern, not an active security threat to users of the extension.

Technical evidence

Scanner reason: zizmor matched workflow-security rule archived-uses. The match applies to this repository.

Contextual assessment: The workflow references an archived GitHub Action for creating releases. Archived actions no longer receive security patches or maintenance. However, this is a CI-only tooling file that runs on merged pull requests to the main branch using the standard GITHUB_TOKEN. No attacker-controlled input reaches the action in a way that demonstrates concrete harm, and the action is an official GitHub-maintained action that was deprecated rather than compromised. The risk is maintainability and future vulnerability exposure, not a current exploit path.

Impact: low · Exploitability: unlikely

Developer action: Replace the archived release action with a maintained alternative, such as using the GitHub CLI release create command directly, and update actions/checkout to a current version.

Scanner
zizmor 1.28.0
Rule
archived-uses
File role
tooling
Source
.github/workflows/release.yml:70
Deterministic technical evidence (3)
  • zizmor reported artipacked · zizmor 1.28.0

    The code has a known weakness, though this scan does not show that anyone can exploit it here.

    Policy reason: zizmor-known-workflow-rule · Execution scope: automation

    Source: .github/workflows/release.yml:21-24

  • zizmor reported unpinned-uses · zizmor 1.28.0

    The code has a known weakness, though this scan does not show that anyone can exploit it here.

    Policy reason: zizmor-known-workflow-rule · Execution scope: automation

    Source: .github/workflows/release.yml:70

  • zizmor reported unpinned-uses · zizmor 1.28.0

    The code has a known weakness, though this scan does not show that anyone can exploit it here.

    Policy reason: zizmor-known-workflow-rule · Execution scope: automation

    Source: .github/workflows/release.yml:22

Related contextual observations

Outdated actions/checkout version

low risk · high confidence

The code checkout step uses an older version of a standard tool. It still works but should be updated for ongoing maintenance.

Technical assessment

The workflow uses actions/checkout@v2, which is an older major version. While not archived, newer versions receive security and functionality updates. This is a maintainability concern in CI tooling with no demonstrated user-facing security impact.

Impact: low · Exploitability: unlikely

Developer action: Update actions/checkout to the latest major version.

Sources:

Coverage and limitations

JavaScript coverage

Unresolved JavaScript stages

Tools

Limitations

Technical scan identity