Who it is for
Replace port numbers with stable, named .localhost URLs for local development. For humans and agents.
README.md:3
PUBLIC REPORT · ADDED BY METAL MANTRA / AGENT SIGNAL v0.2
portless.
Scanned repository says: Replace port numbers with stable, named .localhost URLs for local development. For humans and agents.
Metal Mantra scanned this public repository on its own initiative; the maintainer did not submit it. Maintainers: scan the repository yourself to take this report over, or contact us.
Inspect GitHub source0community interest
Votes show community interest, not safety. They never change this score.
66/100CCCNot security certification
Critical findings need attention.
Critical finding · details withheld for 30 days
Inspect the findingsRuntime safety, real-world agent capability, fitness for your use case or independent certification.
Scan scope79 / 81Partial eligible-file selection · not the entire repository
Recorded findings10Heuristic matches requiring human review
SnapshotOct 12, 2026UTC · engine 0.4.0
DNS at scan timeUnverifiedDomain control is not security certification
What the source
actually tells us.
Structured, cited information from the scanned archive. Repository-authored claims are labeled and never treated as verified capabilities.
79 / 81Partial selection
ReadRepository-authored information
2LICENSE, package.json
What it can do
No explicit capability or integration was extracted; that does not mean none exists.
What adoption takes
macOS, Linux, or Windows
README.md:557Tailscale CLI (optional, for --tailscale and --funnel)
README.md:558ngrok CLI (optional, for --ngrok)
README.md:559Manifest declares Node.js >=24 as a requirement.
package.json:7
Limits and terms
A license or copying file is present; its terms have not been reviewed.
LICENSE:1
Observed technical context
TypeScript · 74 selected filesJavaScript · 5 selected filesModel API reference · static only
These are references in selected source files, not proof that a feature works at runtime.
Read from commit 674c2de at Oct 12, 2026, 5:18 AM UTC. Source links open that exact commit. Repository statements are unreviewed and do not affect the score.
02 / FINDINGS FIRSTWhat needs
What needs
a closer look.
Critical details are withheld publicly for the first 30 days after a scan. A matched pattern is a lead for investigation, not a confirmed vulnerability.
Dependencies: no lockfile or exact version pins at the repository root, so no advisory check was possible.
10 findings
CRITICALCritical finding · details withheld for 30 days
Critical finding · details withheld for 30 days
Details are withheld from public view for 30 days after the scan. The owner can see them in full.
Review the private assessment and address the finding.
CRITICALCritical finding · details withheld for 30 days
Critical finding · details withheld for 30 days
Details are withheld from public view for 30 days after the scan. The owner can see them in full.
Review the private assessment and address the finding.
MAJORTLS certificate checks disabled
TLS certificate checks disabled
The code turns off certificate checking for HTTPS connections. Anyone on the network path can then impersonate the model provider, a tool API or a data source and read or change what the agent sends and receives.
Keep certificate verification on; if a private CA is needed, trust that CA explicitly instead of disabling checks.
MAJORLLM request without token ceiling
LLM request without token ceiling
A model request does not set a maximum output length. One unusual input can produce a very long, expensive response.
Set max_tokens or the provider's equivalent on each model call.
MAJORPublic LLM endpoint without rate limit
Public LLM endpoint without rate limit
A public endpoint calls a model without any visible rate limit. Anyone can send many requests and run up cost or exhaust quota.
Apply per-user or per-IP rate limits before model calls.
MAJORLLM output without runtime schema
LLM output without runtime schema
Model output is used without being checked against a schema. Unexpected or malformed output can break later steps or be trusted when it should not be.
Validate model output with Zod, JSON Schema, Pydantic or provider structured output.
MAJORModel call without fallback
Model call without fallback
A model call has no visible fallback. If the provider fails or is rate limited, the whole agent fails with it.
Configure a secondary model or explicit fallback path for provider failures.
MAJORDomain ownership not verified
Domain ownership not verified
Metal Mantra could not confirm that the owner controls the stated domain. The domain may belong to someone else.
Verify the domain using the Metal Mantra DNS TXT challenge.
MINORPrivacy Policy link not confirmed
Privacy Policy link not confirmed
No privacy policy link was found on the stated homepage. Buyers cannot see how the vendor handles their data.
Expose a clear Privacy Policy link on the official homepage.
MINORTerms link not confirmed
Terms link not confirmed
No terms link was found on the stated homepage. Buyers cannot see the conditions that apply to using the service.
Expose a clear Terms link on the official homepage.
The boundary
is part of the result.
- What was scanned
- 79 of 81 eligible files · Partial selection.
Supported static source patterns and domain checks; no runtime execution. - What remains unknown
- Unscanned files, external dependencies, production configuration, actual agent behavior and evidence beyond the configured checks.
- Source location
- Links open the current repository HEAD. Source may have changed since this snapshot.
- Something looks wrong?
- Tell us if a finding, scope or claim on this report needs a correction. Report a problem with this report
- Entity trust · 15% of v0.2
- Includes DNS ownership, HTTPS and policy evidence. Verification is domain control, not a security certificate.DNS: unverifiedHTTPS: availablePrivacy: not confirmedTerms: not confirmed
Open the
calculation.
Each pillar starts at 100. Rule deductions reduce its score; weights determine the overall contribution.
Security & privacy
54/100
Guardrails & loop control
76/100
Schema & tooling
84/100
Token & cost efficiency
86/100
Entity trust
25/100
Did portless work for people?
No user reports yet.
Each report is one signed-in GitHub account saying what happened. We do not verify that the account ran the agent, and reports never change the automated score or grade. For a security problem, use the disclosure page instead of a public note.
SHARE THE EVIDENCEA signal.
A signal.
Not a seal.
Share the full report so its scope and limits travel with the score.
