Android Google Play FREQUENCE Running
FREQUENCE Running
Current version
2.8.50
com.jby.frequence
No CVE referenced at NVD for FREQUENCE Running on Android. Absence of CVEs is not a guarantee of security.
- Known vulnerabilities
- 0
- Still open
- 0
- KEV open
- 0
- Max CVSS (open)
- -
Known vulnerabilities (CVE)
No CVE is currently referenced in NVD for this app on its platform.
The absence of CVEs is not a security guarantee : it can also mean nobody has audited or published findings.
Cumulative exposure
Low
Weighted sum capped at 100: open CVEs (max 50 pts) + KEV (max 35) + critical shared permissions (max 10) + trackers (max 8) + OS EOL (max 5). Higher score = more exposed.
-
Open CVEs +0/+50
0 open CVEs, max CVSS 0.0, EPSS 0%
-
Active KEVs +0/+35
0 CISA KEVs still open
-
Permissions +0/+10
0 critical shared permission(s)
-
Trackers +0/+8
0 identification/profiling tracker(s)
-
EOL OS +0/+5
Installed OS is end-of-life
Based on permissions only: no CVE data referenced for this app.
Context
Context
Description
Personalized training for 5k, 10k, 21k, marathon, triathlon & trail goals.
Data collected and shared
Source: Play Store Data Safety · 9 data item(s) declared
Indicative classification based on data sensitivity. "Shared" = transmitted to third parties (publisher-declared).
Technical details
- Publisher
- FREQUENCE Running
- Distribution channel
- Google Play
- Identifier
- com.jby.frequence
FAQ
FAQ: FREQUENCE Running
Why are no CVEs listed for FREQUENCE Running?
No CVE is currently referenced in NVD for FREQUENCE Running (com.jby.frequence) with a Android CPE configuration. Either none has been publicly disclosed, or none has been mapped yet. Absence of a CVE is not a security guarantee.
What is the latest known version of FREQUENCE Running?
The most recent version of FREQUENCE Running (com.jby.frequence) tracked by Appaloosa Scout is 2.8.50, published by FREQUENCE Running.
Deploy this app across your fleet
Appaloosa distributes and updates your Android and iOS apps from an enterprise store.