// OWNER · oversecured · REPO SNAPSHOT
oversecured
176 vulnerabilities in Samsung preinstalled Android apps
STARS253+0 · 7d
FORKS61+0 · 7d
CONTRIBUTORS0maintainer graph thin
OPEN ISSUES · PRS0· 0
LICENSE—no license file
LANGUAGEJava
FOUNDED—
LOCATION—
MEMBERS—
PUBLIC REPOS—
TOTAL STARS—
FOCUS—
FUNDING—
//STAR HISTORY · 12M
+253 all-time-window
Stars · cumulative253 · today
//WHY IT'S TRENDING· narrative synthesis · medium confidence
oversecured/Samsung_Vulnerabilities is sitting at #1264 on the trending leaderboard with a pulse of 11/100 with no cross-source channels firing yet — GitHub-stars-only signal so far.
It sits at 253 stars without a fresh weekly delta on record — the trending placement here is steady-state interest in the Java mobile space rather than a 7-day breakout.
Watch-outs: no tagged release on record (treat as pre-stable).
↻ refreshed 55m ago· next sync in 10m· sourced from 0 channels · 0 mentions / 24h
// RELATED REPOS · CROSS-SOURCE OVERLAP
▌ FAQ · answers from the data spine
What is oversecured/Samsung_Vulnerabilities?
176 vulnerabilities in Samsung preinstalled Android apps
Who maintains Samsung_Vulnerabilities?
Maintained by oversecured (the owner) on GitHub.
What language is Samsung_Vulnerabilities written in?
Primarily Java.
When was Samsung_Vulnerabilities created? When was the last update?
Created July 15, 2026 · last commit July 15, 2026.
How do I install Samsung_Vulnerabilities?
Clone the repo:
git clone https://github.com/oversecured/Samsung_Vulnerabilities.gitThen follow the README in the cloned directory.Is Samsung_Vulnerabilities actively maintained?
stalled — no commits for an extended period
Created
Updated
Last commit
//COMMENTS · 0
Sign in to join the discussion