Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/opensource03-harnss-badge.png)](https://mseep.ai/app/opensource03-harnss)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

URL_PAGE="https://mseep.ai/app/opensource03-harnss"
URL_BADGE="https://mseep.net/pr/opensource03-harnss-badge.png"

echo "== HTTP headers =="
for u in "$URL_PAGE" "$URL_BADGE"; do
  echo "--- $u ---"
  curl -sSI "$u" | sed -n '1,15p'
done

echo
echo "== Check listing page for audit transparency signals =="
curl -sL "$URL_PAGE" | rg -ni "methodology|criteria|scope|report|audit|last updated|evidence" -C2 || true

Repository: OpenSource03/harnss

Length of output: 11200


Ensure the security badge links to documentation with clear audit scope and methodology.

The badge image is accessible, but verification shows the linked page does not contain documented audit methodology, scope, or report details. Users clicking this badge should find transparent documentation of what was audited, how, and by whom—otherwise it risks misleading them about your actual security assurance level.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 1, The badge link (the Markdown line containing the
"MseeP.ai Security Assessment Badge" image and the URL
https://mseep.ai/app/opensource03-harnss) currently points to a page that lacks
documented audit scope and methodology; update the target to a page or file that
clearly documents the audit scope, methodology, findings, assessor identity, and
report date (e.g., create SECURITY_AUDIT.md or an external audit URL) and change
the badge link to that URL so users clicking the badge reach transparent audit
documentation.


> [!WARNING]
> Harnss is in early development and issues are to be expected. Please feel free to report bugs and issues in the Issues section.

Expand Down