Is sec_recent_filings_rss_feed_parser safe to use?

sec_recent_filings_rss_feed_parser has no known vulnerabilities on the latest version (0.0.6). DepScope rates its health at 42/100 (high risk).

What is the latest version of sec_recent_filings_rss_feed_parser?

The latest version of sec_recent_filings_rss_feed_parser is 0.0.6, released 2016-04-22.

Does sec_recent_filings_rss_feed_parser have known vulnerabilities?

No known vulnerabilities on the latest version of sec_recent_filings_rss_feed_parser.

Is sec_recent_filings_rss_feed_parser deprecated?

No, sec_recent_filings_rss_feed_parser is actively maintained. Latest release: 0.0.6 (2016-04-22).

What are alternatives to sec_recent_filings_rss_feed_parser?

DepScope has no curated alternatives for sec_recent_filings_rss_feed_parser at this time.

What license does sec_recent_filings_rss_feed_parser use?

sec_recent_filings_rss_feed_parser is licensed under MIT.

sec_recent_filings_rss_feed_parser

hexv0.0.6

XML Parser for the SEC's Latest Filings Feed An example of such a feed can be found here: https://www.sec.gov/cgi-bin/browse-edgar?action=getcurrent&CIK=&type=10-K&company=&dateb=&owner=include&start=0&count=40&output=atom

License MITpermissive6 versions1 maintainers0 deps

vikram7/sec_latest_filings_rss_feed_parser

42

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

0

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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

First published · 2016-02-26T00:49:44.482136Z

Last updated · 2016-04-22T17:54:32.175992Z