USS Upyun
Limited data: USS Upyun has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.
Based on 3 of 5 areas
Capped at 95: not enough support or review data for a full score.
| Ownership | 100 |
|---|---|
| Maintenance | 100 |
| Security | 85 |
| Support | No data |
| Reputation | No data |
Quick answers
- Is USS Upyun still maintained?
- Yes. Last release 17 Sep 2026, 2 releases in the last 24 months. 17 Sep 2026 · wordpress.org
- Who owns USS Upyun, and has it changed hands?
- No change recorded. Main committer shenyanzhi since Mar 2020. 3 Nov 2026 · SVN log
- Was USS Upyun removed from wordpress.org?
- No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
- Is USS Upyun safe?
- 1 known vulnerability, fixed (latest in 1.5.1). Not on the exploited list. 16 Sep 2025 · Wordfence Intelligence
- Is the latest USS Upyun update safe to install?
- No ownership change before 1.5.1. No one-star spike after it. 13 Sep 2025 · Release history
Active signals
Facts we detected, with links to the source.
No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.
Ownership timeline
Who commits to the plugin's code on wordpress.org, over time.
| plugin-master | 27 Mar 2020 to 27 Mar 2020, 1 commits |
|---|---|
| shenyanzhi | 28 Mar 2020 to 17 Sep 2026, 50 commits |
2 committers recorded. No ownership changes recorded since 2020.
Maintenance
- Last release
- 49 days ago
- Releases, 24 months
- 2
- Tested up to
- 7.1 current
- Requires PHP
- 7.0.0 supported 8.2+
| Q1 2024 | 0 |
|---|---|
| Q2 2024 | 0 |
| Q3 2024 | 0 |
| Q4 2024 | 0 |
| Q1 2025 | 1 |
| Q2 2025 | 0 |
| Q3 2025 | 1 |
| Q4 2025 | 0 |
| Q1 2026 | 0 |
| Q2 2026 | 0 |
| Q3 2026 | 0 |
| Q4 2026 | 0 |
Last release 17 Sep 2026. Tested with WordPress 7.1 (current).
Reputation
Last 90 days: no reviews.
| 5 star | 0 |
|---|---|
| 4 star | 0 |
| 3 star | 0 |
| 2 star | 0 |
| 1 star | 0 |
Security record
1 vulnerability in 24 months, patched (latest fixed in 1.5.1).
Show 1 patched vulnerability
| Published | Issue | CVSS | Affected | Fixed in | Days to patch |
|---|---|---|---|---|---|
| 16 Sep 2025 | USS Upyun <= 1.5.0 - Cross-Site Request Forgery | 4.3 | <= 1.5.0 | 1.5.1 | 366 |
Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.
Support
Support history appears after our first snapshots of the forum counts.
Momentum
20+ active installs. History builds with each weekly snapshot.
Momentum history builds with each snapshot.
Facts
| Version | 1.5.1 |
|---|---|
| Author | 沈唁 |
| Added | 28 Mar 2020 |
| Last updated | 17 Sep 2026 |
| Active installs | 20+ |
| Requires WordPress | 4.6 |
| Tested up to | 7.1.4 |
| Requires PHP | 7.0.0 |
| Category | not stated |
| Tags | USS, upyun, 云存储, 又拍云, 对象存储 |
Other plugins by this author: OSS Aliyun, Sync QCloud COS, KODO Qiniu, TextCensor For Articles, MemorialDay, Pangu JS, Baidu TextCensor For Comments, ImageX, Realtimehot Weibo（微博热搜榜）, OBS HuaWeiCloud, Random Look, Push Message To WeChat
Questions
Is USS Upyun still maintained?
Yes. Last release 17 Sep 2026, 2 releases in the last 24 months.
Who owns USS Upyun, and has it changed hands?
No change recorded. Main committer shenyanzhi since Mar 2020.
Was USS Upyun removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026.
Is USS Upyun safe?
1 known vulnerability, fixed (latest in 1.5.1). Not on the exploited list.
Is the latest USS Upyun update safe to install?
No ownership change before 1.5.1. No one-star spike after it.