Clawseccheck 4.4.4 and 4.4.5 retained, clawscan verdict is null, not public

Publisher handle: gl0di
Skill: clawseccheck (https://clawhub.ai/api/v1/skills/clawseccheck)

Two consecutive releases were uploaded successfully and never became public:

Version Uploaded (UTC) Public?
4.4.4 2026-10-24 no, /versions/4.4.4 returns 404
4.4.5 2026-11-03 15:14 no, /versions/4.4.5 returns 404

latestVersion is still 4.4.3, which is public and has a clawscan verdict.

What clawhub scan download clawseccheck --version X returns for both retained versions:

  • manifest.json: status: "succeeded", writtenBack: true (4.4.4: 150 files, 4.4.5: 152 files)
  • clawscan.json, endor.json, skillspector.json, virustotal.json: 5 bytes each (null)
  • static-analysis.json: present (4.4.5: engine v2.4.27, 19 findings, same six reason codes as the public 4.4.3)

The only difference from the public 4.4.3 is that clawscan.json is null instead of a 3 KB verdict. The static findings are the same family as 4.4.3 (the package is a security audit tool, so its own detection signatures contain strings such as exec( and eval(atob().

This looks like the partial-SkillSpector-report regression described in the “Retained ClawHub releases stuck after incomplete security checks” thread. I am not asking for a waiver or bypass. Please re-run the required scans for the two retained uploads. I have not re-uploaded duplicates and will not.

Thank you.

Hey there @gl0di, and welcome to the community!

Thanks for the detailed report, and particularly for preserving the original uploads rather than submitting duplicate versions.

You’re right that this resembles the issue discussed in the earlier retained-release thread. A regression involving partial SkillSpector reports was addressed in ClawScan #129, although we can’t yet confirm that’s the cause of your specific releases being held.

There is a supported way to request fresh scans of existing versions directly, so let’s try that before escalating.

While authenticated as the publisher (clawhub login), run:

clawhub scan --slug clawseccheck --version 4.4.5 --update --json

If that completes successfully, you can do the same for 4.4.4:

clawhub scan --slug clawseccheck --version 4.4.4 --update --json

The --update option writes successful scan results back to the selected version. It does not require uploading another release.

Once those complete, check whether the versions have become publicly available. A successful scan alone doesn’t necessarily clear an existing publication hold.

If either request fails, or both scans succeed but the releases remain hidden, please share the relevant sanitized scan results and publication status here. No need to repeat the static-analysis work you’ve already done.

And please continue to preserve the existing uploads. We don’t want to bypass security checks or create unnecessary duplicate releases.

-Joe

Hi Joe, thanks for the quick answer and for the supported command.

I ran it as publisher (clawhub login, authenticated as gl0di), once per retained version:

clawhub scan --slug clawseccheck --version 4.4.5 --update --json
clawhub scan --slug clawseccheck --version 4.4.4 --update --json

Results:

Version Scan id Outcome
4.4.5 w176fzb5xxasyahh9ae7ty06018hk05n accepted, then CLI exit 1 after ~42 min: Timed out waiting for scan
4.4.4 w178vvrnpd4bvjvh2yqjpfr4tn8hj9ka accepted, then CLI exit 1 after ~42 min: Timed out waiting for scan
  • Both requests were accepted (the CLI printed “Submitting scan” and the server returned a scan id), but neither completed.
  • No JSON was returned, so nothing was written back to either version.
  • GET /api/v1/skills/clawseccheck/versions/4.4.4 and .../versions/4.4.5 still return 404 afterwards.

I have not re-uploaded anything and will not create duplicate releases. 4.4.3 is still the public latest.

Could you check what happened to these two scans on your side, and whether the hold on 4.4.4 and 4.4.5 can be cleared from there?

Thanks,
gl0di