jsc-safe-url
npmv0.2.4TypeScriptUtility functions for converting to and from URLs that encode query string data into URL paths
Not recommended for new projects
No — jsc-safe-url should not be adopted for new projects. Last published 1210 days ago.
- AAdoption: grade A, Excellent.
11M downloads per week and 2 known dependents.
- FMaintenance: grade F, Failing.
Last published 1210 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 5.9 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
0BSD — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding jsc-safe-url to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the jsc-safe-url README.
toJscSafeUrl('https://example.com/path?foo=bar#fragment')
// 'https://example.com/path//&foo=bar#fragment'jsc-safe-url vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| jsc-safe-urlthis page | 11M | 2 | 0BSD | 3 years ago |
| @react-native/metro-config | 4.6M | 6 | MIT | 4 days ago |
| @react-native/metro-babel-transformer | 0 | 3 | MIT | 4 days ago |
| babel-preset-expo | 0 | 1 | MIT | 4 days ago |
| @expo/config | 12.6M | 5 | MIT | 4 days ago |
| expo-file-system | 9.2M | 1 | MIT | 4 days ago |
Dependencies
Declared by jsc-safe-url v0.2.4. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (2)
Used by
Popular packages that depend on jsc-safe-url.
Relationship graph
Dependencies (left) and dependents (right) of jsc-safe-url.
Frequently installed together
The Expo SDK
A JavaScript parser built from the Hermes engine
Turns an AST into code.
Generate errors that contain a code frame that point to source locations.
Lightweight debugging utility for Node.js and the browser
Tool for transforming styles with JS plugins
Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset
Generate source maps
A library for interacting with the app.json
Remap sequential sourcemaps through transformations to point at the original source code
A CSS parser, transformer, and minifier written in Rust
Encode/decode sourcemap mappings
Release history
No releases in the last two years, typically about 0 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 0.2.4latest | 3 years ago | 5.9 KB | 0BSD |
| 0.2.3 | 3 years ago | 5.9 KB | 0BSD |
| 0.2.2 | 3 years ago | 5.9 KB | 0BSD |
| 0.2.1 | 3 years ago | 5.9 KB | 0BSD |
| 0.2.0 | 3 years ago | 10 KB | 0BSD |
| 0.1.0 | 3 years ago | 9.0 KB | 0BSD |
| 0.0.1 | 3 years ago | 8.8 KB | 0BSD |
Overview
jsc-safe-url is an npm package that utility functions for converting to and from URLs that encode query string data into URL paths. It is extremely widely used, with about 11M downloads per week and 2 known dependents in the graph. The latest version is 0.2.4, released under the 0BSD license.
Who should use it
Teams working in the npm ecosystem who need utility functions for converting to and from URLs that encode query string data into URL paths and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (11M weekly downloads).
- Ships TypeScript type definitions.
- Clear open-source license (0BSD).
- Lean dependency tree (2 direct dependencies).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Frequently asked questions
Should I use jsc-safe-url?
No — jsc-safe-url should not be adopted for new projects. Last published 1210 days ago.
How do I install jsc-safe-url?
Run `npm install jsc-safe-url` to add jsc-safe-url to your npm project.
What license is jsc-safe-url released under?
jsc-safe-url is distributed under the 0BSD license.
How popular is jsc-safe-url?
jsc-safe-url has approximately 11,019,173 downloads per week and 2 known dependent packages.
Is jsc-safe-url still maintained?
The most recent release of jsc-safe-url (v0.2.4) was published 3 years ago.
Does jsc-safe-url run install scripts?
No. jsc-safe-url does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.