Summary
open-metadata/OpenMetadata v2026-03-20 was classified as CRITICAL RISK with a risk score of 18933. Sigil detected 2066 findings across 12999 files, covering phases including network exfiltration, code patterns, provenance, install hooks, credential access, obfuscation. Review the findings below before installing this package.
Package description: OpenMetadata is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team co...
v2026-03-20
20 March 2026, 23:54 UTC
by Sigil Bot
Risk Score
18933
Findings
2066
Files Scanned
12999
Provenance
Findings by Phase
Phase Ordering
Phases are ordered by criticality, with the most dangerous at the top. Click any phase header to expand or collapse its findings. Critical phases are expanded by default.
install-makefile-curl
HIGHMakefile/script pipes remote content to shell
repo/.github/workflows/py-nox-ci.yml:54
# Install uv to speed up virtual environments installation
curl -LsSf https://astral.sh/uv/install.sh | sh
pip install noxWhy was this flagged?
A script or Makefile pipes content from a remote URL directly into a shell (curl | sh or wget | bash). This is inherently dangerous because the remote content can change at any time, and the command runs with the current user's permissions. Rated HIGH because it requires manual execution (unlike install hooks) but still executes arbitrary remote code.
install-pip-setup-exec
CRITICALsetup.py executes code at install time
repo/ingestion/tests/unit/lineage/test_lineage_processors.py:80
def setUp(self):
"""Set up test fixtures"""Why was this flagged?
This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.
install-pip-setup-exec
CRITICALsetup.py executes code at install time
repo/openmetadata-integration-tests/src/test/java/org/openmetadata/it/tests/VectorEmbeddingIntegrationIT.java:89
@BeforeEach
void setUp() throws Exception {
Assumptions.assumeTrue(embeddingClient != null, "Embedding client not available");Why was this flagged?
This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.
install-pip-setup-exec
CRITICALsetup.py executes code at install time
repo/openmetadata-service/src/test/java/org/openmetadata/service/search/elasticsearch/ElasticSearchIndexManagerTest.java:65
@BeforeEach
void setUp() {
lenient().when(elasticsearchClient.indices()).thenReturn(indicesClient);Why was this flagged?
This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.
install-pip-setup-exec
CRITICALsetup.py executes code at install time
repo/openmetadata-service/src/test/java/org/openmetadata/service/search/opensearch/OpenSearchIndexManagerTest.java:65
@BeforeEach
void setUp() {
lenient().when(openSearchClient.indices()).thenReturn(indicesClient);Why was this flagged?
This setup.py calls subprocess, os.system, exec, or eval during package installation. Legitimate packages rarely need to execute arbitrary commands at install time. This pattern is commonly used by malicious packages to download and run payloads, exfiltrate environment variables, or establish persistence. Rated CRITICAL because it runs with the installer's full permissions.
install-npm-postinstall
CRITICALnpm lifecycle script — runs automatically on install
repo/openmetadata-ui/src/main/resources/ui/package.json:18
"preview": "vite preview",
"postinstall": "yarn run build-check",
"preinstall": "cd ../../../../.. && yarn install --frozen-lockfile && cd openmetadata-ui-core-components/src/main/resources/ui && yarn install && yarn build",Why was this flagged?
npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.
install-npm-postinstall
CRITICALnpm lifecycle script — runs automatically on install
repo/openmetadata-ui/src/main/resources/ui/package.json:19
"postinstall": "yarn run build-check",
"preinstall": "cd ../../../../.. && yarn install --frozen-lockfile && cd openmetadata-ui-core-components/src/main/resources/ui && yarn install && yarn build",
"test": "jest --passWithNoTests",Why was this flagged?
npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.
install-npm-postinstall
CRITICALnpm lifecycle script — runs automatically on install
repo/package.json:17
"scripts": {
"preinstall": "yarn global add node-gyp@10.0.1",
"test": "echo \"Error: no test specified\" && exit 1"Why was this flagged?
npm lifecycle scripts like postinstall run automatically during package installation with no user interaction required. This is the #1 attack vector for malicious npm packages — attackers embed data theft or backdoor installation in these hooks. Rated CRITICAL because code executes before the developer can review it.
Badge
Markdown
[](https://sigilsec.ai/scans/3E50FFBA-52C5-4B00-83D6-3C80A4F230CD)HTML
<a href="https://sigilsec.ai/scans/3E50FFBA-52C5-4B00-83D6-3C80A4F230CD"><img src="https://sigilsec.ai/badge/github/open-metadata/OpenMetadata" alt="Sigil Scan"></a>Run This Scan Yourself
Scan your own packages
Run Sigil locally to audit any package before it touches your codebase.
Early Access
Get cloud scanning, threat intel, and CI/CD integration.
Join 150+ developers on the waitlist.
Get threat intelligence and product updates
Security research, new threat signatures, and product updates. No spam.
Other github scans
Believe this result is incorrect? Request a review or see our Terms of Service and Methodology.