You can publish a package to GitHub Packages to make the package available for others to download and re-use.
Who can use this feature?Anyone with write permissions for a repository can publish a package to that repository.
About published packagesYou can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. GitHub provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see @Codertocat/hello-world-npm.
You can publish packages in a public repository (public packages) to share with all of GitHub, or in a private repository (private packages) to share with collaborators or an organization. A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. GitHub reviews each published security advisory and may use it to send Dependabot alerts to affected repositories. For more information, see About repository security advisories.
Publishing a packageYou can publish a package to GitHub Packages using any supported package client by following the same general guidelines.
For instructions specific to your package client, see Working with a GitHub Packages registry.
After you publish a package, you can view the package on GitHub. For more information, see Viewing packages.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4