io.github.easytocloud/mac-letterhead
version 0.24.4
- scanned 2026-10-16
- source github.com/easytocloud/Mac-letterhead
- transport stdio
- files read 33
- methodology 0.2.0
- ruleset 0.1.1
100
100
29measured on 75% of this axis
the dependencies in 1 requirements file (tools/requirements.txt) were not measured — it pins no exact version, or could not be read whole — so the score covers the 3 lockfiles that were
95measured on 65% of this axis
58
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.
Auth Posture
- authentication_model
stdio transport: the client launches the server as a subprocess, so the OS process boundary is the auth boundary — `03` §4 does not penalise absent auth here
- transport_security
declared transport: stdio — launched as a subprocess by the client, so the security boundary is the client process, not a network port (`03` §4)
- secret_handling
no committed credential found, and no environment variable with a credential-shaped name is read anywhere in the source
- authorization_granularity
4 tool registrations with conditional access logic present in the same source
Dependency Health
- tools/requirements.txtunpinned requirements
18 vulnerabilities osv-scanner reported at versions it resolved rather than read from a pin (tools/requirements.txt) are not attributed — nobody pinned those versions, so they say nothing about what this server ships
- package-lock.jsonhandlebars 4.7.9 — GHSA-8r5x-fm3f-whwj
transitive, CVSS 9.8, fixed in 4.7.10
https://osv.dev/vulnerability/GHSA-8r5x-fm3f-whwj - package-lock.jsonhandlebars 4.7.9 — GHSA-p8wg-vrv2-v86f
transitive, CVSS 9.2, fixed in 4.7.10
https://osv.dev/vulnerability/GHSA-p8wg-vrv2-v86f - dxt/uv.lockmcp 2.0.0 — GHSA-84m7-p3x7-pcfv
direct, CVSS 7.5, fixed in 2.2.0
https://osv.dev/vulnerability/GHSA-84m7-p3x7-pcfv - uv.lockmcp 2.1.1 — GHSA-84m7-p3x7-pcfv
direct, CVSS 7.5, fixed in 2.2.0
https://osv.dev/vulnerability/GHSA-84m7-p3x7-pcfv - package-lock.jsonbraces 3.0.3 — GHSA-vfj7-8cjw-p6xm
transitive, CVSS 8.7
https://osv.dev/vulnerability/GHSA-vfj7-8cjw-p6xm - package-lock.jsonhttp-cache-semantics 4.2.0 — GHSA-ch52-4w7c-c8xp
transitive, CVSS 8.7
https://osv.dev/vulnerability/GHSA-ch52-4w7c-c8xp - package-lock.jsonbrace-expansion 5.0.9 — GHSA-6j4f-fj2g-mc7p
transitive, CVSS 7.5, fixed in 5.0.10
https://osv.dev/vulnerability/GHSA-6j4f-fj2g-mc7p - package-lock.jsonbrace-expansion 5.0.9 — GHSA-qhr7-859c-m2p7
transitive, CVSS 7.5, fixed in 5.0.11
https://osv.dev/vulnerability/GHSA-qhr7-859c-m2p7 - package-lock.jsonundici 6.28.0 — GHSA-rfgv-xxqx-mfg5
transitive, CVSS 7.5, fixed in 6.28.1
https://osv.dev/vulnerability/GHSA-rfgv-xxqx-mfg5 - package-lock.jsonip-address 10.5.0 — GHSA-2vr4-cq9g-pvrc
transitive, CVSS 6.9, fixed in 10.5.1
https://osv.dev/vulnerability/GHSA-2vr4-cq9g-pvrc - package-lock.jsonip-address 10.5.0 — GHSA-h3mg-xc3c-68pw
transitive, CVSS 6.3, fixed in 10.7.1
https://osv.dev/vulnerability/GHSA-h3mg-xc3c-68pw - package-lock.jsonip-address 10.5.0 — GHSA-j6r3-76f7-8jcv
transitive, CVSS 6.3, fixed in 10.7.1
https://osv.dev/vulnerability/GHSA-j6r3-76f7-8jcv - package-lock.jsonip-address 10.5.0 — GHSA-rpw4-54j3-4h4q
transitive, CVSS 6.3, fixed in 10.5.1
https://osv.dev/vulnerability/GHSA-rpw4-54j3-4h4q - package-lock.jsonpostcss-selector-parser 7.1.4 — GHSA-rj75-hqrm-r3gf
transitive, CVSS 5.9, fixed in 7.1.6
https://osv.dev/vulnerability/GHSA-rj75-hqrm-r3gf - package-lock.jsonundici 6.28.0 — GHSA-3wwx-pv8p-q78v
transitive, CVSS 5.9, fixed in 6.28.1
https://osv.dev/vulnerability/GHSA-3wwx-pv8p-q78v - package-lock.jsonbrace-expansion 5.0.9 — GHSA-q2hr-2g5m-vwhr
transitive, CVSS 5.3, fixed in 5.0.12
https://osv.dev/vulnerability/GHSA-q2hr-2g5m-vwhr - package-lock.jsonhandlebars 4.7.9 — GHSA-xw65-4hp5-5hc7
transitive, CVSS 4.7, fixed in 4.7.10
https://osv.dev/vulnerability/GHSA-xw65-4hp5-5hc7 - package-lock.jsonundici 6.28.0 — GHSA-r53p-7pc4-xj5r
transitive, CVSS 3.7, fixed in 6.28.1
https://osv.dev/vulnerability/GHSA-r53p-7pc4-xj5r
Maintenance
- recency
last commit 11 day(s) before 2026-10-16
- issue_responsiveness
every issue read was filed by the project itself (6 by its maintainers or bots), so none is someone outside waiting for an answer, and `03` §5's question — will anyone read an issue I file? — has nothing to measure.
- release_cadence
released 11 day(s) ago (by releases), inside `03` §5's 30-day window
- bus_factor
2 regular authors in the last 12 months
- repository_signals
`03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.
Transparency
- license
LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text
- readme_quality
README.md: installation instructions (+25), configuration documented (+25), exposed tools or resources enumerated (+30), states what the server does in the first 200 words (+20)
- declared_scopes
neither the README nor the MCP manifest documents what the server accesses or what side effects it has
- changelog
CHANGELOG.md present
- security_contact
no SECURITY.md and no disclosure contact in the README, so a finder has no route to report a vulnerability privately
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.