TavernKeeper Scan Report

Manjove1/forged-by-primus-portfolio

Commit 02ee241 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.

Deterministic technical evidence (4)
  • zizmor reported template-injection · 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:36

  • 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:28

  • 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:99

  • 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:27-30

Contextual expected matches (1)

zizmor reported superfluous-actions

Expected behavior · high confidence

The workflow uses a popular third-party GitHub Action to create releases. While the same result could be achieved with a built-in command, using this action is standard practice and poses no security risk.

Technical evidence

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

Contextual assessment: The zizmor superfluous-actions rule flags that softprops/action-gh-release@v2 duplicates functionality available via the GitHub CLI already installed on the runner. This is an informational best-practice finding, not a security vulnerability. The action is pinned to a major version (v2), is widely used for creating GitHub Releases, and the workflow only uses it to publish a pre-built zip artifact. No credential exfiltration, code execution, or data flow concerns are present. The scanner severity is info, confirming this is a style/efficiency note rather than a security threat.

Impact: none · Exploitability: unlikely

Developer action: Consider replacing the third-party release action with the built-in GitHub CLI if you want to reduce third-party dependency, but this is optional and not security-critical.

Scanner
zizmor 1.28.0
Rule
superfluous-actions
File role
tooling
Source
.github/workflows/release.yml:99

Coverage and limitations

JavaScript coverage

Tools

Limitations

Technical scan identity