Is alarm_clock safe to use?

alarm_clock has no known vulnerabilities on the latest version (0.1.1). DepScope rates its health at 49/100 (high risk).

What is the latest version of alarm_clock?

The latest version of alarm_clock is 0.1.1, released 2017-10-04.

Does alarm_clock have known vulnerabilities?

No known vulnerabilities on the latest version of alarm_clock.

Is alarm_clock deprecated?

No, alarm_clock is actively maintained. Latest release: 0.1.1 (2017-10-04).

What are alternatives to alarm_clock?

DepScope has no curated alternatives for alarm_clock at this time.

What license does alarm_clock use?

alarm_clock is licensed under MIT.

alarm_clock

hexv0.1.1

:timer.send_after/3 persistable. Allows scheduling message delivery to specified process in miliseconds or at specified Calendar.DateTime. AlarmClock will make sure that messages are delivered using retry mechanism and after it's own crash, since all messages can be persisted.

License MITpermissive6 versions1 maintainers0 deps11,509 weekly dl

burmajam/alarm_clock

/ 100

Health

safe to use

[email protected] is safe to use (health: 49/100)

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

12/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/alarm_clock

First published · 2016-12-10T23:37:32.032118Z

Last updated · 2017-10-04T10:28:55.745558Z