Skip to content
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

Inconsistencies in how deprecation metadata is stored across package ecosystems #1029

Open
jasminewang0 opened this issue Jan 30, 2025 · 0 comments
Open

Inconsistencies in how deprecation metadata is stored across package ecosystems #1029

jasminewang0 opened this issue Jan 30, 2025 · 0 comments

Comments

@jasminewang0
Copy link

Poking around the data today and I noticed that deprecated NPM packages (ex. sntp) have a status: deprecated, but deprecated NuGet packages (ex. microsoft.net.compilers) don't have the deprecated status stored into a specific field. Would be great to have consistent data fields across different package ecosystems.

Thank you!
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
1 participant
@jasminewang0