Gathering detailed insights and metrics for xml-name-validator
Gathering detailed insights and metrics for xml-name-validator
Gathering detailed insights and metrics for xml-name-validator
Gathering detailed insights and metrics for xml-name-validator
Validates whether a string matches the production for an XML name or qualified name
npm install xml-name-validator
99.3
Supply Chain
65.6
Quality
81.6
Maintenance
100
Vulnerability
100
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
15 Stars
29 Commits
10 Forks
6 Watching
1 Branches
6 Contributors
Updated on 11 May 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
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
3
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.
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.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
1 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
Found 3/25 approved changesets -- score normalized to 1
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
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