| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help |
The search service can find package by either name (apache), provides(webserver), absolute file names (/usr/bin/apache), binaries (gprof) or shared libraries (libXm.so.2) in standard path. It does not support multiple arguments yet...
The System and Arch are optional added filters, for example System could be "redhat", "redhat-7.2", "mandrake" or "gnome", Arch could be "i386" or "src", etc. depending on your system.
The npm-name command-line tool checks whether a package or organization name is available on npm. Why would I use npm-name rather than npm’s built-in search? 1. Nicer & simpler output 2. Squatter detection (https://github.com/sholladay/squatter) 3. Supports checking the availability of organization names 4. Performance
| Package | Summary | Distribution | Download |
| npm-name-cli-4.0.1-12.el9.noarch.html | Check whether a package or organization name is available on npm | EPEL 9 for ppc64le | npm-name-cli-4.0.1-12.el9.noarch.rpm |
| npm-name-cli-4.0.1-12.el9.noarch.html | Check whether a package or organization name is available on npm | EPEL 9 for x86_64 | npm-name-cli-4.0.1-12.el9.noarch.rpm |
| npm-name-cli-4.0.1-12.el9.noarch.html | Check whether a package or organization name is available on npm | EPEL 9 for aarch64 | npm-name-cli-4.0.1-12.el9.noarch.rpm |
| npm-name-cli-4.0.1-12.el9.noarch.html | Check whether a package or organization name is available on npm | EPEL 9 for s390x | npm-name-cli-4.0.1-12.el9.noarch.rpm |
Generated by rpm2html 1.6