gitsafehub
github.com/tomakehurst/build-pipeline-plugin ↗

tomakehurst/build-pipeline-plugin

scanned 2026-08-11 · git c5bcbfd
2 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 secrets✓Vulnerable dependencies2Known OSS vulnerabilities8Risky 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ⓘ 2 found

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

  • Worth fixing CVE-2017-1000084 Parameterized Trigger Plugin fails to check Item/Build permission
    pom.xml
    A package you depend on has a known security hole (CVE-2017-1000084). Fix: Update that package to its patched version.
  • Minor CVE-2022-27195 jenkins-2-plugins/parameterized-trigger: Information disclosure
    pom.xml
    A package you depend on has a known security hole (CVE-2022-27195). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 8 found · 2 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-qg25-hgjv-cg9q Improper Neutralization of Special Elements in Output Used by a Downstream Component in Apache Groovy
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2015-3253). Fix: Update that package to its patched version.
  • Serious GHSA-xphj-m9cc-8fmq Deserialization of Untrusted Data in Groovy
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2016-6814). Fix: Update that package to its patched version.
  • Worth fixing GHSA-269g-pwp5-87pp TemporaryFolder on unix-like systems does not limit access to created files
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2020-15250). Fix: Update that package to its patched version.
  • Worth fixing GHSA-6fg4-36v7-xv32 Stored Cross-site Scripting vulnerability in Jenkins Dashboard View Plugin
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2022-27197). Fix: Update that package to its patched version.
  • Worth fixing GHSA-fv4q-4h24-23qr Jenkins Dashboard View Plugin vulnerable to Cross-site Scripting
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2019-10396). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jwhm-9cjm-4493 Cross-site Scripting in Jenkins Dashboard View Plugin
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2021-21649). Fix: Update that package to its patched version.
  • Worth fixing GHSA-mc22-25r3-2w9w Parameterized Trigger Plugin fails to check Item/Build permission
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2017-1000084). Fix: Update that package to its patched version.
  • Minor GHSA-5mpf-hw8f-86w9 Sensitive parameter values captured in build metadata files by Jenkins Parameterized Trigger Plugin
    /workdirs/scan-a9385199-44ca-4c45-be73-2f5f76aed788/pom.xml
    A package you depend on has a known security hole (CVE-2022-27195). 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.