Is Attest safe?
Probably. Read the findings first.
Use with care. Some checks failed or could not be verified.
What to know before installing
- highcurl | sh in a script
Public scan report
scanner v0.1.3 · 2026-09-19 · same rubric, same numbers if you re-run it
1 high1 medium
- Code scan125 source files scanned8/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (2)
- mediumNetwork call to a raw IP address
net.raw-ipattestlayer-0.1.0/attest/gateway/server.py: …, and recorded. Addressing (either): http://127.0.0.1:8322/https://api.hubapi.com/crm/v3/objects/de…
- highcurl | sh in a script
install.curl-pipeattestlayer-0.1.0/deploy/bootstrap.sh: … ! command -v docker >/dev/null; then curl -fsSL https://get.docker.com | sh fi command -v git >/dev/null || (apt-ge…
Overall 57/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON