Why do devs object to using unsupported open source in production?

Asked 2 years ago

I'm looking for the best practice for dealing with unsupported open-source dependencies. I've seen a few options, but I'm not sure which is the best. For example, should I fork the project and continue development? Or should I just use a different project?

Open-source dependencies Software dependencies

Anderson Prince

Tuesday, June 07, 2022

There's no easy answer when it comes to dealing with dead open-source dependencies. It really depends on the project and how important it is to you. If the project is essential to your application, then you may want to consider forking it and continuing development yourself. If it's not as important, then you may be able to get away with using a different project.

Write an answer...﻿

Cancel

Please follow our Community Guidelines

Why do devs object to using unsupported open source in production?

Related Posts

How do I generate a package-lock.json file?

What are the benefits of using a package manager like npm?

How do I add a module as a dependency in my POM file?

Why is the AWS SAM CLI ignoring my Python dependencies during build, package, and deploy?

How do I use requirements.txt to install all dependencies in a python project?

How to avoid circular dependencies in python?

Are dependency constraints in dart pub files necessary?

How do I get AWS SAM CLI to stop ignoring my Python dependencies during the deployment process?

I have some non-python dependencies that needs paths. How do you set it up?

Should Flutter dependencies be upgraded automatically?

Can't find what you're looking for?