Is huoxin/allow-own-discussion-rename safe to use?

huoxin/allow-own-discussion-rename has no known vulnerabilities on the latest version (v0.0.1). DepScope rates its health at 46/100 (high risk).

What is the latest version of huoxin/allow-own-discussion-rename?

The latest version of huoxin/allow-own-discussion-rename is v0.0.1, released 2025-09-30.

Does huoxin/allow-own-discussion-rename have known vulnerabilities?

No known vulnerabilities on the latest version of huoxin/allow-own-discussion-rename.

Is huoxin/allow-own-discussion-rename deprecated?

No, huoxin/allow-own-discussion-rename is actively maintained. Latest release: v0.0.1 (2025-09-30).

What are alternatives to huoxin/allow-own-discussion-rename?

DepScope has no curated alternatives for huoxin/allow-own-discussion-rename at this time.

What license does huoxin/allow-own-discussion-rename use?

huoxin/allow-own-discussion-rename is licensed under MIT.

huoxin/allow-own-discussion-rename

composervv0.0.1

Force allow renaming of own discussion

License MITpermissive1 versions1 maintainers1 deps

huoxin233/flarum-ext-allow-own-discussion-rename

/ 100

Health

use with caution

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

Moderate health score (46/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

flarum/core

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/composer/huoxin/allow-own-discussion-rename

Last updated · 2025-09-30T11:34:35+00:00