Is merge_into_polyfill safe to use?

merge_into_polyfill has no known vulnerabilities on the latest version (0.4.0). DepScope rates its health at 36/100 (critical risk).

What is the latest version of merge_into_polyfill?

The latest version of merge_into_polyfill is 0.4.0, released 2025-01-15.

Does merge_into_polyfill have known vulnerabilities?

No known vulnerabilities on the latest version of merge_into_polyfill.

Is merge_into_polyfill deprecated?

No, merge_into_polyfill is actively maintained. Latest release: 0.4.0 (2025-01-15).

What are alternatives to merge_into_polyfill?

DepScope has no curated alternatives for merge_into_polyfill at this time.

What license does merge_into_polyfill use?

merge_into_polyfill is licensed under MIT.

merge_into_polyfill

hexv0.4.0

DSL and polyfill to express MERGE queries using ecto (postgres adapter only)

License MITpermissive5 versions1 maintainers0 deps13 weekly dl

ZennerIoT/merge_into_polyfill

/ 100

Health

use with caution

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

Low health score (36/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/hex/merge_into_polyfill

First published · 2023-04-13T12:14:51.445349Z

Last updated · 2025-01-15T16:04:57.003986Z