Gathering detailed insights and metrics for xmlchars
Gathering detailed insights and metrics for xmlchars
Gathering detailed insights and metrics for xmlchars
Gathering detailed insights and metrics for xmlchars
Utilities for determining if characters belong to character classes defined by the XML specs.
npm install xmlchars
99.3
Supply Chain
78.4
Quality
75.4
Maintenance
100
Vulnerability
100
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
3 Stars
236 Commits
2 Forks
3 Watching
11 Branches
3 Contributors
Updated on 24 Sept 2024
Minified
Minified + Gzipped
TypeScript (98.93%)
JavaScript (1.07%)
Cumulative downloads
Total Downloads
Last day
-23.6%
3,196,710
Compared to previous day
Last week
-4.9%
21,865,021
Compared to previous week
Last month
13.3%
90,708,636
Compared to previous month
Last year
13.3%
885,936,328
Compared to previous year
Utilities for determining whether characters belong to character classes defined by the XML specs.
It used to be that the library was contained in a single file and you could just
import/require/what-have-you the xmlchars
module. However, that setup did not
work well for people who cared about code optimization. Importing xmlchars
meant importing all of the library and because of the way the code was
generated there was no way to shake the resulting code tree.
Different modules cover different standards. At the time this documentation was last updated, we had:
xmlchars/xml/1.0/ed5
which covers XML 1.0 edition 5.xmlchars/xml/1.0/ed4
which covers XML 1.0 edition 4.xmlchars/xml/1.1/ed2
which covers XML 1.0 edition 2.xmlchars/xmlns/1.0/ed3
which covers XML Namespaces 1.0 edition 3.The "things" each module contains can be categorized as follows:
"Fragments": these are parts and pieces of regular expressions that correspond to the productions defined in the standard that the module covers. You'd use these to build regular expressions.
Regular expressions that correspond to the productions defined in the standard that the module covers.
Lists: these are arrays of characters that correspond to the productions.
Functions that test code points to verify whether they fit a production.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
3 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
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-25
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