Skip to content

Removed ecosystem_specific field #5407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Nardonist opened this issue Mar 26, 2025 · 2 comments
Open

Removed ecosystem_specific field #5407

Nardonist opened this issue Mar 26, 2025 · 2 comments

Comments

@Nardonist
Copy link

Why was the ecosystem_specific field with the vulnerable functions described removed?
For example, GHSA-3f63-hfp8-52jq had this field with the described eval function, on February 13 the ecosystem_specific field was removed. But in the vulnerability description itself, information about this function is present
@tatianahub
Copy link

I fully agree with @Nardonist. I also notice that there are no vulnerabilities with the 'ecosystem_specific' field in the advisory database now. It is not only about GHSA-3f63-hfp8-52jq.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Nardonist @tatianahub and others