Gathering detailed insights and metrics for registry-url
Gathering detailed insights and metrics for registry-url
Installations
npm install registry-urlDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Min. Node Version
>=18
Node Version
23.6.1
NPM Version
10.9.2
Score
99.1
Supply Chain
77.8
Quality
85.4
Maintenance
100
Vulnerability
100
License
Releases
8
Languages
2
JavaScript
TypeScript
JavaScript (95.77%)
TypeScript (4.23%)
Developer
sindresorhus
Download Statistics
Total Downloads
2,902,284,085
Last Day
634,476
Last Week
11,536,312
Last Month
45,464,500
Last Year
487,820,170
GitHub Statistics
MIT License
55 Stars
57 Commits
17 Forks
7 Watchers
1 Branches
12 Contributors
Updated on Apr 22, 2025
Bundle Size
4.18 kB
Minified
1.93 kB
Minified + Gzipped
Sponsor this package
Maintainers
1
Package Meta Information
Latest Version
7.2.0
Package Id
registry-url@7.2.0
Unpacked Size
4.89 kB
Size
2.04 kB
File Count
5
NPM Version
10.9.2
Node Version
23.6.1
Published on
Apr 15, 2025
Total Downloads
Cumulative downloads
Total Downloads
2,902,284,085
Last Day
-9%
634,476
Compared to previous day
Last Week
9.4%
11,536,312
Compared to previous week
Last Month
-2%
45,464,500
Compared to previous month
Last Year
6.7%
487,820,170
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
2
registry-url
Get the set npm registry URL
It's usually https://registry.npmjs.org/, but it's configurable.
Use this if you do anything with the npm registry as users will expect it to use their configured registry.
Install
1npm install registry-url
Usage
1# .npmrc 2registry = 'https://custom-registry.com/'
1import registryUrl, {defaultUrl} from 'registry-url'; 2 3console.log(registryUrl()); 4//=> 'https://custom-registry.com/' 5 6console.log(defaultUrl); 7//=> 'https://registry.npmjs.org/'
It can also retrieve the registry URL associated with an npm scope.
1# .npmrc 2@myco:registry = 'https://custom-registry.com/'
1import registryUrl from 'registry-url'; 2 3console.log(registryUrl('@myco')); 4//=> 'https://custom-registry.com/'
If the provided scope is not in the user's .npmrc file, then registry-url will check for the existence of registry, or if that's not set, fallback to the default npm registry.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
security policy file detected
Details
- Info: security policy file detected: .github/security.md:1
- Info: Found linked content: .github/security.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: .github/security.md:1
- Info: Found text in security policy: .github/security.md:1
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: license:0
- Info: FSF or OSI recognized license: MIT License: license:0
Reason
9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
Reason
Found 13/30 approved changesets -- score normalized to 4
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/main.yml:1
- Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/registry-url/main.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/sindresorhus/registry-url/main.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/main.yml:22
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 13 are checked with a SAST tool
Score
5.2
/10
Last Scanned on 2025-05-05
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More