Is fluent-plugin-rename-key safe to use?

fluent-plugin-rename-key has no known vulnerabilities on the latest version (0.4.1). DepScope rates its health at 51/100 (high risk).

What is the latest version of fluent-plugin-rename-key?

The latest version of fluent-plugin-rename-key is 0.4.1, released 2017-05-22.

Does fluent-plugin-rename-key have known vulnerabilities?

No known vulnerabilities on the latest version of fluent-plugin-rename-key.

Is fluent-plugin-rename-key deprecated?

No, fluent-plugin-rename-key is actively maintained. Latest release: 0.4.1 (2017-05-22).

What are alternatives to fluent-plugin-rename-key?

Popular alternatives to fluent-plugin-rename-key in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does fluent-plugin-rename-key use?

fluent-plugin-rename-key is licensed under Apache-2.0.

fluent-plugin-rename-key

rubygemsv0.4.1

Fluentd output plugin. Rename keys which match given regular expressions, assign new tags and re-emit the records.

License Apache-2.0permissive8 versions1 deps10,154,641 weekly dl

shunwen/fluent-plugin-rename-key

/ 100

Health

use with caution

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

Moderate health score (51/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Quality signals

OSS Criticality

0.46medium

Health History

Dependency Tree

License Audit

Dependencies (1)

fluentd

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/fluent-plugin-rename-key