xml-name-validator
npmv5.0.0Validates whether a string matches the production for an XML name or qualified name
Adopt with care
xml-name-validator is usable, with caveats. Last published 1033 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- DMaintenance: grade D, Poor — a real concern.
Last published 1033 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 13 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 6 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
Apache-2.0 — 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 xml-name-validator 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
- node >=18
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the xml-name-validator README.
"use strict":
const xnv = require("xml-name-validator");
// Will return true
xnv.name("x");
xnv.name(":");
xnv.name("a:0");
xnv.name("a:b:c");
// Will return false
xnv.name("\\");
xnv.name("'");
xnv.name("0");
xnv.name("a!");xml-name-validator 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 |
|---|---|---|---|---|
| xml-name-validatorthis page | 0 | 2 | Apache-2.0 | 2 years ago |
| xml-naming | 0 | 2 | MIT | 19 hours ago |
| dom-serializer | 94.3M | 2 | MIT | 1 day ago |
| cheerio | 24.1M | 5 | MIT | 1 day ago |
| plist | 14M | 2 | MIT | 1 day ago |
| fast-xml-parser | 0 | 4 | MIT | 1 day ago |
Dependencies
Declared by xml-name-validator v5.0.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (3)
Used by
Popular packages that depend on xml-name-validator.
Relationship graph
Dependencies (left) and dependents (right) of xml-name-validator.
Frequently installed together
An AST-based pattern checker for JavaScript.
An implementation of the WHATWG URL Standard's URL API and parsing machinery
An HTTP/1.1 client, written from scratch for Node.js
Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.
An arbitrary-precision Decimal type for JavaScript.
Implements the WebIDL algorithms for converting to and from JavaScript values
Parses, serializes, and manipulates MIME types, according to the WHATWG MIME Sniffing Standard
CSS color - Resolve and convert CSS colors.
A per-spec XML serializer implementation
CSS syntax patches for CSS tree
A tool set for CSS: fast detailed parser (CSS → AST), walker (AST traversal), generator (AST → CSS) and lexer (validation and matching) based on specs and browser implementations
Sniff the encoding from a HTML byte stream
Release history
No releases in the last two years, typically about 971 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 5.0.0latest | 2 years ago | 13 KB | Apache-2.0 |
| 4.0.0 | 5 years ago | 13 KB | Apache-2.0 |
| 3.0.0 | 9 years ago | — | Apache-2.0 |
| 2.0.1 | 11 years ago | — | WTFPL |
| 1.0.0 | 11 years ago | — | WTFPL |
Overview
xml-name-validator is an npm package that validates whether a string matches the production for an XML name or qualified name. It has 2 known dependents in the graph. The latest version is 5.0.0, released under the Apache-2.0 license.
Who should use it
Teams working in the npm ecosystem who need validates whether a string matches the production for an XML name or qualified name and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (Apache-2.0).
- Lean dependency tree (3 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use xml-name-validator?
xml-name-validator is usable, with caveats. Last published 1033 days ago.
How do I install xml-name-validator?
Run `npm install xml-name-validator` to add xml-name-validator to your npm project.
What license is xml-name-validator released under?
xml-name-validator is distributed under the Apache-2.0 license.
How popular is xml-name-validator?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on xml-name-validator.
Is xml-name-validator still maintained?
The most recent release of xml-name-validator (v5.0.0) was published 2 years ago.
Does xml-name-validator run install scripts?
No. xml-name-validator does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.