@vaadin/router
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:jouni.me | AI (email-domain): Legacy maintainer email on long-established package; not evidence of this release being malicious. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publish gap explained by known-maintainer resumed activity, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established Vaadin package predating Sigstore provenance adoption; absence is expected for this package's age. | ai |
v2.0.0
3 findingsMaintainer email '[email protected]' uses domain 'jouni.me' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sunzhewyq) than the most recent previously approved version (platosha) on 2024-10-15, but sunzhewyq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.