-
Notifications
You must be signed in to change notification settings - Fork 8
Issues: open-services/open-registry
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Registry is down - npm.open-registry.dev let's encrypt certificate expired yesterday
#45
opened Jul 30, 2020 by
reimertz
Corrupted JSON on https://npm.open-registry.dev/wrappy URL
bug
Something isn't working
#44
opened Mar 25, 2020 by
afel
Production go-ipfs going bananas
breaking-production
Issues that needs to be fixed ASAP as they affect production negatively
bug
Something isn't working
#39
opened May 16, 2019 by
victorb
Fetching packages via dnslink
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
#37
opened May 15, 2019 by
victorb
Make sure 404s from registry.npmjs.org gets 404 response from open-registry
bug
Something isn't working
good first issue
Good for newcomers
#29
opened May 1, 2019 by
victorb
Cache original metadata response without rewriting
bug
Something isn't working
good first issue
Good for newcomers
#24
opened Apr 25, 2019 by
victorb
package metadata has wrong MIME type
bug
Something isn't working
good first issue
Good for newcomers
#18
opened Apr 25, 2019 by
drewfish
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.