npmpackage.info

Gathering detailed insights and metrics for is-potential-custom-element-name

Other packages similar to is-potential-custom-element-name

@types/is-potential-custom-element-name

1.0.0

TypeScript definitions for is-potential-custom-element-name

Gathering detailed insights and metrics for is-potential-custom-element-name

is-potential-custom-element-name - 1.0.1 | npmpackage.info

is-potential-custom-element-name

Check whether a given string matches the `PotentialCustomElementName` production as defined in the HTML Standard.

1.0.1

MIT

JavaScript

288.00 B

3.3

Installations

npm install is-potential-custom-element-name

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

14.15.0

NPM Version

6.14.8 Score

99.7

Supply Chain

Quality

75.1

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

1

Closed

0

Merged

1

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

mathiasbynens

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

9 Stars

5 Commits

4 Forks

2 Watchers

1 Branches

2 Contributors

Updated on Sep 08, 2023

Bundle Size

566.00 B

Minified

288.00 B

Minified + Gzipped

Bundlephobia

Maintainers

View All 2 Contributors

Package Meta Information

Latest Version

1.0.1

Package Id

is-potential-custom-element-name@1.0.1

Size

1.86 kB

NPM Version

6.14.8

Node Version

14.15.0

Published on

Apr 07, 2021

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

mocha regenerate

is-potential-custom-element-name

is-potential-custom-element-name checks whether a given string matches the PotentialCustomElementName production as defined in the HTML Standard.

Installation

To use is-potential-custom-element-name programmatically, install it as a dependency via npm:

1$ npm install is-potential-custom-element-name

Then, require it:

1const isPotentialCustomElementName = require('is-potential-custom-element-name');

Usage

1isPotentialCustomElementName('foo-bar');
2// → true
3isPotentialCustomElementName('Foo-bar');
4// → false
5isPotentialCustomElementName('baz-©');
6// → false
7isPotentialCustomElementName('annotation-xml');
8// → true

Author


Mathias Bynens

License

is-potential-custom-element-name is available under the MIT license.

No vulnerabilities found.

10

Binary-Artifacts

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

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

2

Code-Review

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

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

Security-Policy

Determines if the project has published a security policy.

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

3.3

/10

Last Scanned on 2025-05-05

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