Package Health Score

60 / 100

security
No known security issues
popularity
Recognized
maintenance
Inactive
community
Sustainable

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

Version				Vulnerabilities	License Risk
2.0.0	\|	10/2023	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.7	\|	04/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.21	\|	11/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.0.43	\|	04/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

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

Recognized

Weekly Downloads (26,861)

GitHub Stars: 506
Forks: 65
Contributors: 20

Direct Usage Popularity

The npm package web-component-analyzer receives a total of 26,861 downloads a week. As such, we scored web-component-analyzer popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package web-component-analyzer, we found that it has been starred 506 times.

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

Community

Sustainable

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

With more than 10 contributors for the web-component-analyzer repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like web-component-analyzer is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 80
Open PR: 12
Last Release: 1 year ago
Last Commit: 1 year ago

Further analysis of the maintenance status of web-component-analyzer based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for web-component-analyzer is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

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: not defined

Age: 6 years
Dependencies: 4 Direct
Versions: 106
Install Size: 722 kB
Dist-tags: 2
# of Files: 459
Maintainers: 4
TS Typings: Yes

web-component-analyzer 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 web-component-analyzer?

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

runem / lit-analyzer / packages / lit-analyzer / src / analyze / default-lit-analyzer-context.ts View on Github

private findComponentsInFile(sourceFile: SourceFile) {
		const analyzeResult = analyzeComponents(sourceFile, {
			checker: this.checker,
			ts: this.ts,
			config: { diagnostics: true, analyzeLibDom: true, excludedDeclarationNames: ["HTMLElement"] }
		});

		// Forget
		const existingResult = this.definitionStore.getAnalysisResultForFile(sourceFile);
		if (existingResult != null) {
			this.htmlStore.forgetCollection(
				{
					tags: existingResult.componentDefinitions.map(d => d.tagName),
					events: existingResult.globalEvents.map(e => e.name),
					attrs: []
				},
				HtmlDataSourceKind.DECLARED
			);

View more ways to use web-component-analyzer

web-component-analyzer

Web component analyzer GIF

web-component-analyzer is a CLI that makes it possible to easily analyze web components. It analyzes your code and jsdoc in order to extract properties, attributes, methods, events, slots, css shadow parts and css custom properties. Works with both javascript and typescript.

Try the online playground here

In addition to vanilla web components this tool supports web components built with the following libraries:

➤ Installation

$ npm install -g web-component-analyzer

$ npx web-component-analyzer src

➤ Usage

$ wca analyze
$ wca analyze src --format markdown
$ wca analyze "src/**/*.{js,ts}" --outDir components
$ wca analyze my-element.js --outFile custom-elements.json
$ wca analyze --outFiles {dir}/custom-element.json

The analyze command analyses an optional <input> and emits the output to the console as default. When the <input> is omitted it will find all components excluding node_modules. The default format is markdown.

Options

Option	Type	Description
`--format`	`markdown` \| `json` \| `vscode`	Specify output format. Default is `markdown`.
`--outDir

web-component-analyzer dependencies

fast-glob ts-simple-type typescript yargs

FAQs

What is web-component-analyzer?

CLI that analyzes web components. Visit Snyk Advisor to see a full health score report for web-component-analyzer, including popularity, security, maintenance & community analysis.

Is web-component-analyzer popular?

The npm package web-component-analyzer receives a total of 26,861 weekly downloads. As such, web-component-analyzer popularity was classified as a recognized. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is web-component-analyzer well maintained?

We found indications that web-component-analyzer is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is web-component-analyzer safe to use?

The npm package web-component-analyzer 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 8 November-2024, at 02:06 (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

web-component-analyzer

CLI that analyzes web components For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (26,861)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use web-component-analyzer?

web-component-analyzer

➤ Installation

➤ Usage

Options

web-component-analyzer dependencies

web-component-analyzer development dependencies

FAQs

What is web-component-analyzer?

Is web-component-analyzer popular?

Is web-component-analyzer well maintained?

Is web-component-analyzer safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (26,861)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use web-component-analyzer?

web-component-analyzer

➤ Installation

➤ Usage

Options

web-component-analyzer dependencies

web-component-analyzer development dependencies

FAQs

What is web-component-analyzer?

Is web-component-analyzer popular?

Is web-component-analyzer well maintained?

Is web-component-analyzer safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues