npmpackage.info

Gathering detailed insights and metrics for xml-name-validator

Other packages similar to xml-name-validator

@types/xml-name-validator

4.0.3

TypeScript definitions for xml-name-validator

sax

1.4.1

An evented streaming XML parser in JavaScript

@babel/helper-validator-identifier

7.25.9

Validate identifier/keywords name

@trysound/sax

0.2.0

An evented streaming XML parser in JavaScript

Gathering detailed insights and metrics for xml-name-validator

xml-name-validator

Validates whether a string matches the production for an XML name or qualified name

5.0.0

Apache-2.0

JavaScript

4,302,951,179 4.2

Installations

npm install xml-name-validator

Score

99.3

Supply Chain

65.6

Quality

81.6

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

9

Closed

2

Merged

7

Issues

Open

0

Total

2

Closed

2

Releases

5.0.0

v5.0.0

Published on 12 Nov 2023

4.0.0

v4.0.0

Published on 18 Sept 2021

3.0.0

v3.0.0

Published on 23 Oct 2017

2.0.1

v2.0.1

Published on 24 Feb 2015

2.0.0

v2.0.0

Published on 22 Feb 2015

1.0.0

v1.0.0

Published on 22 Feb 2015

View all 6 releases

Developer

jsdom

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=18

Typescript Support

No

Node Version

21.1.0

NPM Version

10.2.0 Statistics

15 Stars

29 Commits

10 Forks

6 Watching

1 Branches

6 Contributors

Updated on 11 May 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

4,302,951,179

Last day

-8%

5,108,374

Compared to previous day

Last week

2.6%

30,392,382

Compared to previous week

Last month

22.5%

118,945,205

Compared to previous month

Last year

15.1%

1,105,792,115

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@domenic/eslint-config benchmark eslint

Versions

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.

1"use strict":
2const xnv = require("xml-name-validator");
3
4// Will return true
5xnv.name("x");
6xnv.name(":");
7xnv.name("a:0");
8xnv.name("a:b:c");
9
10// Will return false
11xnv.name("\\");
12xnv.name("'");
13xnv.name("0");
14xnv.name("a!");
15
16// Will return true
17xnv.qname("x");
18xnv.qname("a0");
19xnv.qname("a:b");
20
21// Will return false
22xnv.qname(":a");
23xnv.qname(":b");
24xnv.qname("a:b:c");
25xnv.qname("a:0");

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Security-Policy

Determines if the project has published a security policy.

9

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

4.2

/10

Last Scanned on 2024-11-18

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