← Home

@vaadin/polymer-legacy-adapter

npm Repository Homepage
39
Versions
—
License
No
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-sunzhewyqsissbruecker

Keywords

Vaadinweb-componentsweb-componentpolymer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Vaadin internal adapter package; sparse README/description is consistent across all 519 versions of this org's packages. ai

Versions (showing 39 of 39)

Version Deps Published
24.10.3 3 / 7
24.10.2 3 / 7
24.10.1 3 / 7
24.10.0 3 / 7
24.9.16 3 / 7
24.9.15 3 / 7
24.9.14 3 / 7
24.9.13 3 / 7
24.9.12 3 / 7
24.9.11 3 / 7
24.9.10 3 / 7
24.9.9 3 / 7
24.9.8 3 / 7
24.9.7 3 / 7
24.9.6 3 / 7
24.9.5 3 / 7
24.9.4 3 / 7
24.9.3 3 / 7
24.9.2 3 / 7
24.9.1 3 / 7
24.8.14 3 / 7
24.8.13 3 / 7
24.8.12 3 / 7
24.8.11 3 / 7
24.8.10 3 / 7
24.8.8 3 / 7
24.8.7 3 / 7
24.8.6 3 / 7
24.8.4 3 / 7
24.8.2 3 / 7
24.8.1 3 / 7
24.7.12 3 / 7
24.7.10 3 / 7
24.7.7 3 / 7
24.7.6 3 / 7
24.6.11 3 / 7
24.6.10 3 / 7
23.6.4 3 / 6
23.6.3 3 / 6

v24.10.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.10.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.10.1

1 finding
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.

v24.10.0

1 finding
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.

v24.9.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.9.3

1 finding
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.

v24.9.2

2 findings
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.

v24.9.1

2 findings
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.

v24.8.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.8.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.8.12

1 finding
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.

v24.8.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.8.10

1 finding
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.

v24.8.8

2 findings
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.

v24.8.7

2 findings
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.

v24.8.6

2 findings
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.

v24.8.4

2 findings
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.

v24.8.2

2 findings
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.

v24.8.1

2 findings
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.

v24.7.12

2 findings
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.

v24.7.10

2 findings
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.

v24.7.7

2 findings
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.

v24.7.6

2 findings
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.

v24.6.11

2 findings
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.

v24.6.10

2 findings
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.

v23.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v23.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.