gitsafehub
github.com/tecnologia-da-informacao-br/calendar ↗

tecnologia-da-informacao-br/calendar

scanned 2026-08-10 · git f6e1267
1 of 6 checks flagged a security issue
🟡 Worth a look
Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies✓Known OSS vulnerabilities7Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ none found ✓

Packages you depend on that have known security holes (CVEs).

Nothing found by this check. ✓

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 7 found

Your dependencies cross-checked against the OSV vulnerability database.

  • Worth fixing GHSA-5gvw-p9qm-jgwh jackson-databind: @JsonView bypassed for @JsonUnwrapped container properties on deserialization
    /workdirs/scan-cb2b4893-6f4e-4ebe-9dfa-d8415170a7c4/backend/pom.xml
    A package you depend on has a known security hole (CVE-2026-59889). Fix: Update that package to its patched version.
  • Worth fixing GHSA-frvp-7c67-39w9 Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`)
    /workdirs/scan-cb2b4893-6f4e-4ebe-9dfa-d8415170a7c4/frontend/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Worth fixing GHSA-54fx-42gc-7vw4 Hono: Algorithmic Complexity DoS in Language Middleware
    /workdirs/scan-cb2b4893-6f4e-4ebe-9dfa-d8415170a7c4/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-71848). Fix: Update that package to its patched version.
  • Worth fixing GHSA-8j4g-w8fx-2239 Hono: ReDoS in CORS middleware via Access-Control-Request-Headers
    /workdirs/scan-cb2b4893-6f4e-4ebe-9dfa-d8415170a7c4/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-69207). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f23p-vx2j-j53r Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosure
    /workdirs/scan-cb2b4893-6f4e-4ebe-9dfa-d8415170a7c4/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-71850). Fix: Update that package to its patched version.
  • Worth fixing GHSA-2v37-7h3g-55p8 nanoid: custom generators can loop indefinitely when size is zero
    /workdirs/scan-cb2b4893-6f4e-4ebe-9dfa-d8415170a7c4/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-67213). Fix: Update that package to its patched version.
  • Minor GHSA-79qm-7rj5-m7r9 Hono: Proxy Helper does not remove response headers listed in the `Connection` header
    /workdirs/scan-cb2b4893-6f4e-4ebe-9dfa-d8415170a7c4/frontend/package-lock.json
    A package you depend on has a known security hole (CVE-2026-71849). Fix: Update that package to its patched version.

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ none found ✓

Packages that look intentionally malicious: typosquats, sneaky install scripts.

Nothing found by this check. ✓

via Guarddog v2.10.0 · Apache-2.0

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.