gitsafehub
github.com/davidkpiano/azure-ts-node-starter ↗

davidkpiano/azure-ts-node-starter

scanned 2026-08-13 · git 25ef6a0
3 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

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

Leaked secrets7Vulnerable dependencies85Known OSS vulnerabilities209Risky code patternsMalicious dependenciesProject health

Security checks

Leaked secrets — Gitleaks 7 found · 5 serious

API keys, passwords or tokens committed into the repo.

  • Serious facebook-secret Discovered a Facebook Application secret, posing a risk of unauthorized access to Facebook accounts and personal data exposure.
    .env.example:16
    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 facebook-secret Discovered a Facebook Application secret, posing a risk of unauthorized access to Facebook accounts and personal data exposure.
    .env.example:7
    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 twitter-api-secret Found a Twitter API Secret, risking the security of Twitter app integrations and sensitive data access.
    .env.example:22
    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 facebook-secret Discovered a Facebook Application secret, posing a risk of unauthorized access to Facebook accounts and personal data exposure.
    .env.example: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 twitter-api-key Identified a Twitter API Key, which may compromise Twitter application integrations and user data security.
    .env.example:21
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    .env.example:16
    A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
  • Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
    .env.example:25
    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 85 found · 11 serious

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

  • Serious CVE-2020-7610 bson: Deserialization of Untrusted Data could result in Code injection or Excessive CPU load
    package-lock.json
    A package you depend on has a known security hole (CVE-2020-7610). Fix: Update that package to its patched version.
  • Serious GHSA-4vmm-mhcq-4x9j Sandbox Bypass Leading to Arbitrary Code Execution in constantinople
    package-lock.json
    A package you depend on has a known security hole (GHSA-4vmm-mhcq-4x9j). Fix: Update that package to its patched version.
  • Serious CVE-2018-1000620 nodejs-cryptiles: Insecure randomness causes the randomDigits() function returns a pseudo-random data string biased to certain digits
    package-lock.json
    A package you depend on has a known security hole (CVE-2018-1000620). Fix: Update that package to its patched version.
  • Serious CVE-2025-7783 form-data: Unsafe random function in form-data
    package-lock.json
    A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
  • Serious CVE-2021-3918 nodejs-json-schema: Prototype pollution vulnerability
    package-lock.json
    A package you depend on has a known security hole (CVE-2021-3918). Fix: Update that package to its patched version.
  • Serious CVE-2019-10744 nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying properties
    package-lock.json
    A package you depend on has a known security hole (CVE-2019-10744). Fix: Update that package to its patched version.
  • Serious CVE-2019-17426 Improper Input Validation in Automattic Mongoose
    package-lock.json
    A package you depend on has a known security hole (CVE-2019-17426). Fix: Update that package to its patched version.
  • Serious CVE-2023-3696 Mongoose Prototype Pollution vulnerability
    package-lock.json
    A package you depend on has a known security hole (CVE-2023-3696). Fix: Update that package to its patched version.
  • Serious CVE-2025-23061 Mongoose search injection vulnerability
    package-lock.json
    A package you depend on has a known security hole (CVE-2025-23061). Fix: Update that package to its patched version.
  • Serious CVE-2019-5413 nodejs-morgan: Unescaped input in compile() function
    package-lock.json
    A package you depend on has a known security hole (CVE-2019-5413). Fix: Update that package to its patched version.
  • Serious CVE-2020-7769 This affects the package nodemailer before 6.4.16. Use of crafted reci ...
    package-lock.json
    A package you depend on has a known security hole (CVE-2020-7769). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-15366 nodejs-ajv: prototype pollution via crafted JSON schema in ajv.validate function
    package-lock.json
    A package you depend on has a known security hole (CVE-2020-15366). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-69873 ajv: ReDoS via $data reference
    package-lock.json
    A package you depend on has a known security hole (CVE-2025-69873). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-43138 async: Prototype Pollution in async
    package-lock.json
    A package you depend on has a known security hole (CVE-2021-43138). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-43138 async: Prototype Pollution in async
    package-lock.json
    A package you depend on has a known security hole (CVE-2021-43138). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-45590 body-parser: Denial of Service Vulnerability in body-parser
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-45590). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-13863 nodejs-bson: Regular expression denial of service in decimal128.js
    package-lock.json
    A package you depend on has a known security hole (CVE-2018-13863). Fix: Update that package to its patched version.
  • Worth fixing CVE-2019-2391 Incorrect parsing of certain JSON input may result in js-bson not corr ...
    package-lock.json
    A package you depend on has a known security hole (CVE-2019-2391). Fix: Update that package to its patched version.
  • Worth fixing CVE-2024-29041 express: cause malformed URLs to be evaluated
    package-lock.json
    A package you depend on has a known security hole (CVE-2024-29041). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-16492 nodejs-extend: Prototype pollution can allow attackers to modify object properties
    package-lock.json
    A package you depend on has a known security hole (CVE-2018-16492). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-12143 form-data: form-data: Form field override via CRLF injection
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-12143). Fix: Update that package to its patched version.
  • Worth fixing CVE-2022-29167 hawk: REDoS in hawk.utils.parseHost() when parsing Host header
    package-lock.json
    A package you depend on has a known security hole (CVE-2022-29167). Fix: Update that package to its patched version.
  • Worth fixing CVE-2018-16487 lodash: Prototype pollution in utilities function
    package-lock.json
    A package you depend on has a known security hole (CVE-2018-16487). Fix: Update that package to its patched version.
  • Worth fixing CVE-2020-8203 nodejs-lodash: prototype pollution in zipObjectDeep function
    package-lock.json
    A package you depend on has a known security hole (CVE-2020-8203). Fix: Update that package to its patched version.
  • Worth fixing CVE-2021-23337 nodejs-lodash: command injection via template
    package-lock.json
    A package you depend on has a known security hole (CVE-2021-23337). Fix: Update that package to its patched version.
… 60 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scanner 209 found · 27 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2023-45133). Fix: Update that package to its patched version.
  • Serious GHSA-v8w9-2789-6hhr Deserialization of Untrusted Data in bson
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2020-7610). Fix: Update that package to its patched version.
  • Serious GHSA-4vmm-mhcq-4x9j Sandbox Bypass Leading to Arbitrary Code Execution in constantinople
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Serious GHSA-rq8g-5pc5-wrhr Insufficient Entropy in cryptiles
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2018-1000620). Fix: Update that package to its patched version.
  • Serious GHSA-hr2v-3952-633q Prototype Pollution in deep-extend
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2018-3750). Fix: Update that package to its patched version.
  • Serious GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
  • Serious GHSA-fjxv-7rqg-78g4 form-data uses unsafe random function in form-data for choosing boundary
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2025-7783). Fix: Update that package to its patched version.
  • Serious MAL-2023-462 Malicious code in fsevents (npm)
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole. Fix: Update that package to its patched version.
  • Serious GHSA-8r6j-v8pm-fqw3 Code injection in fsevents
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2023-45311). Fix: Update that package to its patched version.
  • Serious GHSA-2w6w-674q-4c4q Handlebars.js has JavaScript Injection via AST Type Confusion
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-33937). Fix: Update that package to its patched version.
  • Serious GHSA-765h-qjxv-5f44 Prototype Pollution in handlebars
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2021-23383). Fix: Update that package to its patched version.
  • Serious GHSA-f2jv-r9rf-7988 Remote code execution in handlebars when compiling templates
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2021-23369). Fix: Update that package to its patched version.
  • Serious GHSA-w457-6q6x-cgp9 Prototype Pollution in handlebars
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2019-19919). Fix: Update that package to its patched version.
  • Serious GHSA-896r-f27r-55mw json-schema is vulnerable to Prototype Pollution
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2021-3918). Fix: Update that package to its patched version.
  • Serious GHSA-jf85-cpcp-j695 Prototype Pollution in lodash
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2019-10744). Fix: Update that package to its patched version.
  • Serious GHSA-xvch-5gv4-984h Prototype Pollution in minimist
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2021-44906). Fix: Update that package to its patched version.
  • Serious GHSA-xvch-5gv4-984h Prototype Pollution in minimist
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2021-44906). Fix: Update that package to its patched version.
  • Serious GHSA-8687-vv9j-hgph Improper Input Validation in Automattic Mongoose
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2019-17426). Fix: Update that package to its patched version.
  • Serious GHSA-9m93-w8w6-76hh Mongoose Prototype Pollution vulnerability
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2023-3696). Fix: Update that package to its patched version.
  • Serious GHSA-h8hf-x3f4-xwgp Mongoose Vulnerable to Prototype Pollution in Schema Object
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2022-24304). Fix: Update that package to its patched version.
  • Serious GHSA-m7xq-9374-9rvx Mongoose search injection vulnerability
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2024-53900). Fix: Update that package to its patched version.
  • Serious GHSA-vg7j-7cwx-8wgw Mongoose search injection vulnerability
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2025-23061). Fix: Update that package to its patched version.
  • Serious GHSA-gwg9-rgvj-4h5j Code Injection in morgan
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2019-5413). Fix: Update that package to its patched version.
  • Serious GHSA-48ww-j4fc-435p Command injection in nodemailer
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2020-7769). Fix: Update that package to its patched version.
  • Serious GHSA-w7jw-789q-3m8p shell-quote quote() does not escape newlines in object .op values
    /workdirs/scan-38644e1f-bb1d-434e-8e51-6380a47d530e/package-lock.json
    A package you depend on has a known security hole (CVE-2026-9277). Fix: Update that package to its patched version.
… 184 more not shown

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 timed out

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

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

via Guarddog v2.10.0 · Apache-2.0

error: npm:timeout

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.