xml-name-validator

v5.0.0

Validates whether a string matches the production for an XML name or qualified name For more information about how to use this package see README

Latest version published 5 months ago

License: Apache-2.0

NPM

GitHub

Package Health Score

75 / 100

security
No known security issues
popularity
Influential project
maintenance
Healthy
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
5.0.0	\|	11/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.0.0	\|	09/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.0.0	\|	10/2017		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.1	\|	02/2015		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.0	\|	12/2014		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Apache-2.0

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (17,340,049)

GitHub Stars: 14
Forks: 8
Contributors: 2

Direct Usage Popularity

The npm package xml-name-validator receives a total of 17,340,049 downloads a week. As such, we scored xml-name-validator popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package xml-name-validator, we found that it has been starred 14 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 2
Funding: Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like xml-name-validator is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 5 months ago
Last Commit: 5 months ago

Further analysis of the maintenance status of xml-name-validator based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that xml-name-validator demonstrates a positive version release cadence with at least one new version released in the past 12 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=18

Age: 9 years
Dependencies: 0 Direct
Versions: 8
Install Size: 13.6 kB
Dist-tags: 1
# of Files: 4
Maintainers: 6
TS Typings: No

xml-name-validator has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use xml-name-validator?

To help you get started, we've collected the most common ways that xml-name-validator is being used within popular public projects.

auth0 / node-saml / lib / saml20.js View on Github

function getNameFormat(name){
  if (is_uri(name)){
    return 'urn:oasis:names:tc:SAML:2.0:attrname-format:uri';
  }

  //  Check that the name is a valid xs:Name -> https://www.w3.org/TR/xmlschema-2/#Name
  //  xmlNameValidate.name takes a string and will return an object of the form { success, error }, 
  //  where success is a boolean 
  //  if it is false, then error is a string containing some hint as to where the match went wrong.
  if (xmlNameValidator.name(name).success){
    return 'urn:oasis:names:tc:SAML:2.0:attrname-format:basic';
  }

  // Default value
  return 'urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified';
}

View more ways to use xml-name-validator

Validate XML Names and Qualified Names

This package simply tells you whether or not a string matches the Name or QName productions in the XML Namespaces specification. We use it for implementing the validate algorithm in jsdom, but you can use it for whatever you want.

Usage

This package's main module exports two functions, name() and qname(). Both take a string and return a boolean indicating whether or not the string matches the relevant production.

"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!");

// Will return true
xnv.qname("x");
xnv.qname("a0");
xnv.qname("a:b");

// Will return false
xnv.qname(":a");
xnv.qname(":b");
xnv.qname("a:b:c");
xnv.qname("a:0");

xml-name-validator development dependencies

@domenic/eslint-config benchmark eslint

FAQs

What is xml-name-validator?

Validates whether a string matches the production for an XML name or qualified name. Visit Snyk Advisor to see a full health score report for xml-name-validator, including popularity, security, maintenance & community analysis.

Is xml-name-validator popular?

The npm package xml-name-validator receives a total of 17,340,049 weekly downloads. As such, xml-name-validator popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is xml-name-validator well maintained?

We found that xml-name-validator demonstrated a healthy version release cadence and project activity. It has a community of 2 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is xml-name-validator safe to use?

The npm package xml-name-validator was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 19 April-2024, at 01:03 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP