Is afterpay/afterpay-magento-2-metapackage safe to use?

afterpay/afterpay-magento-2-metapackage has no known vulnerabilities on the latest version (4.4.2). DepScope rates its health at 52/100 (high risk).

What is the latest version of afterpay/afterpay-magento-2-metapackage?

The latest version of afterpay/afterpay-magento-2-metapackage is 4.4.2, released 2026-01-27.

Does afterpay/afterpay-magento-2-metapackage have known vulnerabilities?

No known vulnerabilities on the latest version of afterpay/afterpay-magento-2-metapackage.

Is afterpay/afterpay-magento-2-metapackage deprecated?

No, afterpay/afterpay-magento-2-metapackage is actively maintained. Latest release: 4.4.2 (2026-01-27).

What are alternatives to afterpay/afterpay-magento-2-metapackage?

DepScope has no curated alternatives for afterpay/afterpay-magento-2-metapackage at this time.

What license does afterpay/afterpay-magento-2-metapackage use?

afterpay/afterpay-magento-2-metapackage is licensed under OSL-3.0.

afterpay/afterpay-magento-2-metapackage

composerv4.4.2

Riverty Payment Module for Magento 2 Metapackage

License OSL-3.0network copyleft34 versions2 deps

https://bitbucket.org/afterpay-plugins/afterpay-magento-2-metapackage

/ 100

Health

use with caution

afterpay/[email protected] low health (52/100) — consider alternatives

Moderate health score (52/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

arvato/afterpay-magento-2-extension magento/module-payment

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/composer/afterpay/afterpay-magento-2-metapackage

Last updated · 2026-01-27T11:56:53+00:00