io.github.paiml/pforge

version 0.1.2

No tag matching version 0.1.2 was found in this repository, so the scan read the default branch instead. The findings below describe that code, not necessarily the released version.

Code Safetyweight 30

91

12 vendored or minified paths were excluded before scanning; machine-generated bundles are not the server's own code

Auth Postureweight 20

not assessed

the registry entry declares no transport, so `03` §4's stdio carve-out cannot be applied either way

Dependency Healthweight 20

not assessed

185 vulnerabilities were found and none could be placed in `03` §6's table — no CVSS score, or an ecosystem whose manifest we cannot parse for direct-vs-transitive

Maintenanceweight 15

66measured on 90% of this axis

Transparencyweight 15

65

The evidence

Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.

Code Safety

Auth Posture

Dependency Health

Showing the 50 most severe of 185 findings on this axis. The score was computed over all of them — findings beyond the fourth of a severity still deduct at a tenth of their weight — so the remainder is omitted from this page, not from the arithmetic.

Maintenance

Transparency

Contest a finding

Every number here comes from a rule reading published source, and rules get things wrong. If something on this page is incorrect — or correct but mitigated by a check the rule cannot see — open an issue and we answer it in writing. A finding we got wrong is removed and the rule is fixed; one that stands is answered on the record.

Anyone can file: the maintainer, a researcher who disagrees with the classification, or a user who tested the server and could not reproduce it. Name this server and the rule or advisory ID shown beside the finding above. We aim to reply within five business days and to resolve within ten.

Open an appeal on GitHub