@vaadin/vaadin-usage-statistics
1
Versions
—
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
web-padawandiegocardosoalvarezguilleplatoshajounimanoloyuriyyevvaadin-ownertomivirkkiartur-sunzhewyqsosa-vaadin
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs local check.cjs (bundled in files array) to manage Vaadin usage statistics opt-in/out — documented behavior stable across all versions of this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.1.3 | 1 / 4 |
v2.1.3
3 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: node check.cjs
HIGH
Unclaimed maintainer email domain: jouni.me
email-domain
Maintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.