github.com/michael-hawker/msgraph-sdk-dotnet-auth ↗

michael-hawker/msgraph-sdk-dotnet-auth

scanned 2026-08-11 · git ae832df

3 of 6 checks flagged a security issue

🔴 Needs attention

Only 5 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets4Vulnerable dependencies1Known OSS vulnerabilities1Risky code patterns✓Malicious dependencies✓Project health—

Security checks

Leaked secrets — Gitleaksⓘ 4 found · 4 serious

API keys, passwords or tokens committed into the repo.

Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.

src/Microsoft.Graph.Auth.Test/ConfidentialClient/OnBehalfOfProviderTests.cs:119

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.

src/Microsoft.Graph.Auth.Test/Helpers/JwtHelpersTests.cs:13

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.

src/Microsoft.Graph.Auth.Test/Helpers/JwtHelpersTests.cs:24

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Serious jwt Uncovered a JSON Web Token, which may lead to unauthorized access to web applications and sensitive user data.

src/Microsoft.Graph.Auth.Test/ConfidentialClient/OnBehalfOfProviderTests.cs:18

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 1 found

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

Worth fixing CVE-2024-21907 Improper Handling of Exceptional Conditions in Newtonsoft.Json

samples/WPF.Interactive.Net45.Sample/packages.config

A package you depend on has a known security hole (CVE-2024-21907). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 1 found

Your dependencies cross-checked against the OSV vulnerability database.

Worth fixing GHSA-5crp-9r3c-p9vr Improper Handling of Exceptional Conditions in Newtonsoft.Json

/workdirs/scan-1bcec918-2139-4e3a-9827-c4b5d1bd9fef/samples/WPF.Interactive.Net45.Sample/packages.config

A package you depend on has a known security hole (CVE-2024-21907). 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.