Skip to content

SDK v2#450

Merged
pileks merged 73 commits intodevelopfrom
pileks/met-49-restructure-sdk
Apr 29, 2026
Merged

SDK v2#450
pileks merged 73 commits intodevelopfrom
pileks/met-49-restructure-sdk

Conversation

@pileks
Copy link
Copy Markdown
Contributor

@pileks pileks commented Apr 15, 2026

No description provided.

pileks and others added 30 commits January 8, 2026 22:34
…e proposal has already passed but not been finalized yet
…AOproject/programs into pileks/met-5-optimistic-governance
@socket-security
Copy link
Copy Markdown

socket-security Bot commented Apr 27, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​metadaoproject/​programs@​0.1.0-alpha.1791009892100

View full report

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Apr 28, 2026

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
High CVE: npm flatted vulnerable to unbounded recursion DoS in parse() revive phase

CVE: GHSA-25h7-pfq9-p65f flatted vulnerable to unbounded recursion DoS in parse() revive phase (HIGH)

Affected versions: < 3.4.0

Patched version: 3.4.0

From: ?npm/eslint@9.38.0npm/flatted@3.3.3

ℹ Read more on: This package | This alert | What is a CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/flatted@3.3.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
High CVE: Prototype Pollution via parse() in NodeJS npm flatted

CVE: GHSA-rf6f-7fwh-wjgh Prototype Pollution via parse() in NodeJS flatted (HIGH)

Affected versions: < 3.4.2

Patched version: 3.4.2

From: ?npm/eslint@9.38.0npm/flatted@3.3.3

ℹ Read more on: This package | This alert | What is a CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/flatted@3.3.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@pileks pileks marked this pull request as ready for review April 28, 2026 17:11
@pileks pileks changed the base branch from pileks/met-5-optimistic-governance to develop April 28, 2026 18:32
@metanallok
Copy link
Copy Markdown

Should we also take this time and publish this as metadaoproject/programs to match the repo?

@pileks
Copy link
Copy Markdown
Contributor Author

pileks commented Apr 29, 2026

@metanallok it's done. :)

@pileks pileks merged commit 0c50a34 into develop Apr 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants