npmpackage.info

Gathering detailed insights and metrics for @vaadin/vaadin-usage-statistics

@vaadin/vaadin-usage-statistics

Development-time usage statistics collector.

2.1.3

Apache-2.0

HTML

10,000,362 4.6

Installations

npm install @vaadin/vaadin-usage-statistics

Pull Requests

Open

0

Total

70

Closed

3

Merged

67

Issues

Open

3

Total

14

Closed

11

Releases

v2.1.3

Published on 30 Aug 2024

v2.1.2

Published on 27 Jan 2022

v2.1.1

Published on 25 Jan 2022

v2.1.0

Published on 20 Nov 2019

v2.0.11

Published on 08 Oct 2019

v2.0.10

Published on 30 Aug 2019

View all 28 releases

Developer

vaadin

Developer Guide

BETA

Module System

ESM

Min. Node Version

^12.20.0 || ^14.13.1 || >=16.0.0

Typescript Support

No

Node Version

18.20.1

NPM Version

10.5.0 Statistics

8 Stars

203 Commits

6 Forks

10 Watching

5 Branches

103 Contributors

Updated on 27 Sept 2024

Languages

HTML (64.79%)

JavaScript (35.21%)

Total Downloads

Cumulative downloads

Total Downloads

10,000,362

Last day

-5%

18,103

Compared to previous day

Last week

1.5%

97,010

Compared to previous week

Last month

7.3%

413,107

Compared to previous month

Last year

62.9%

3,418,502

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@vaadin/vaadin-development-mode-detector

Dev Dependencies

@web-padawan/gen-typescript-declarations web-component-tester wct-browser-legacy @webcomponents/webcomponentsjs

Versions

Gathers usage statistics for components used during application development

To be able to understand and focus development more efficiently, Vaadin gathers product usage statistics during development time and ties this to users who are logged in to their Vaadin account. No statistics or other data is collected from the users of the applications based on any Vaadin technologies.

Statistics are only gathered when the application is in development mode. Statistics are automatically disabled and the statistics gathering code is automatically excluded from production builds.

Collected data

Vaadin products used in the application, including version numbers
Frameworks used in the application, including version numbers
Flow features used in the application, including version numers
The first and last time a product was used
The first time statistics were gathered
Your Vaadin user account
Whether you are a Vaadin Pro user or not (true/false)
Browser user-agent string
The IP address the statistics is sent from

Opting out

npm and Vaadin 14+ (using npm)

Using npm, you can disable it for the machine by running

npm explore @vaadin/vaadin-usage-statistics -- npm run disable

or you can disable it for the project by adding

   "vaadin": { "disableUsageStatistics": true }

to your project package.json and running npm install again (remove node_modules if needed).

You can verify this by checking that vaadin-usage-statistics.js contains an empty function.

Vaadin 10 - 14 (using Bower)

Add to your pom.xml:

<dependency>
  <groupId>org.webjars.bowergithub.vaadin</groupId>
  <artifactId>vaadin-usage-statistics</artifactId>
  <version>1.0.0-optout</version>
</dependency>

Bower

To opt-out from statistics, install the no-op version of the vaadin-usage-statistics package using

bower install --save vaadin/vaadin-usage-statistics#optout

You can verify this by checking that vaadin-usage-statistics.html is empty.

If you have any questions on the use of the statistics, please contact statistics@vaadin.com.

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.

5

Maintained

Determines if the project is "actively maintained".

5

Code-Review

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

1

Pinned-Dependencies

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

0

Token-Permissions

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

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

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

4.6

/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