io.github.tlkc888-Jenkins/joy

version 2.40.0

Code Safetyweight 30

11measured on 99% of this axis

5 findings in test code are listed but not deducted; 8 vendored or minified paths were excluded before scanning; machine-generated bundles are not the server's own code; 1 file could not be parsed and was not scanned

Auth Postureweight 20

61measured on 85% of this axis

Dependency Healthweight 20

0measured on 61% of this axis

2 vulnerabilities could not be placed in `03` §6's table and are listed but not scored; the dependencies in 3 requirements files (agents/code-reviewer/requirements.txt, agents/researcher/requirements.txt, joy-telegram/requirements.txt) were not measured — they pin no exact version, or could not be read whole — so the score covers the 5 lockfiles that were

Maintenanceweight 15

not assessed

this server's declared repository could not be read through the GitHub API, so `03` §5's maintenance signals were not retrieved — note that a private repository and an absent one are indistinguishable from outside

Transparencyweight 15

53

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

Showing the 50 most severe of 54 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.

Auth Posture

Dependency Health

Showing the 49 most severe of 433 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