-
Notifications
You must be signed in to change notification settings - Fork 182
Feature/mms support foundation #317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
stappmus
wants to merge
9
commits into
capcom6:master
Choose a base branch
from
stappmus:feature/mms-support-foundation
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+12,009
−1,926
Draft
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
c2c9a6b
[mms] establish attachment metadata contract for incoming MMS
stappmus 5c620f6
[mms] persist inbound attachment metadata for durable processing
stappmus 7de02dd
[mms] add outbound JSON and multipart media request pipeline
stappmus e84361a
[mms] secure local media storage with signed access and retention
stappmus 60a936e
[mms] document media contract and enforce settings validation coverage
stappmus a25eb3c
[mms] wire carrier MMS transport into queued outbound flow
stappmus 23c5b6d
[ui] refresh app shell and home visuals for clearer operations
stappmus fb72ffa
[mms] publish API contract updates for media and carrier guidance
stappmus 545afd4
Finalize MMS support and build fixes
stappmus File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
klinkerapps android-smsmms library maintenance status 2025💡 Result:
As of 2025, KlinkerApps’
android-smsmmsappears to be effectively unmaintained:5.2.6dated Jan 28, 2020. [2]android-smsmms/directory “Last Modified” in Dec 2025, which can reflect repository syncing/metadata updates rather than new library development. [5]Bottom line: for 2025, plan on no active maintainer support and be prepared to fork/patch if you depend on it.
Sources: [1] [2] [3] [4] [5]
🌐 Web query:
com.klinkerapps android-smsmms version 5.2.6 maven central💡 Result:
Artifact
com.klinkerapps:android-smsmms:5.2.6is present on Maven Central (packaging: AAR) and is available under: (repo1.maven.org)Gradle:
implementation "com.klinkerapps:android-smsmms:5.2.6"(MvnRepository also lists 5.2.6 as the “New Version” for this artifact.) (mvnrepository.com)
Citations:
🌐 Web query:
klinkerapps android-smsmms security vulnerabilities CVE💡 Result:
Are there CVEs specifically for KlinkerApps / Pulse SMS (Android SMS/MMS app)?
I could not find any public CVE entries in NVD that explicitly name Klinker Apps or the Pulse SMS Android package (
xyz.klinker.messenger). (That doesn’t prove none exist—only that none appear to be publicly cataloged/attributed that way.)Relevant Android SMS/MMS CVEs you should be aware of (platform-level, not Klinker-specific)
These are examples of SMS/MMS-stack or messaging-app vulnerabilities that have affected Android or Google’s messaging components:
ACTION_SENDTOintents in certain conditions. (nvd.nist.gov)Pulse SMS “cloud sync” security claim (not a CVE)
Pulse SMS’s support docs state that messages stored on their servers are encrypted using your password and claim they cannot decrypt/read them. (support.pulsesms.app)
If you tell me which specific KlinkerApps app you mean (Pulse SMS vs other Klinker apps) and whether you want CVE-only results or also non-CVE disclosures/advisories, I can narrow the search further.
Citations:
Reconsider dependency on unmaintained
com.klinkerapps:android-smsmms:5.2.6.Version 5.2.6 exists on Maven Central but the library is effectively unmaintained: the last release (v5.2.5) was October 2019, with no code activity for ~5 years and no active maintainer support. While no specific CVEs are publicly cataloged for this library, relying on an unmaintained dependency for core MMS transport is a significant long-term risk—you will need to fork/patch if critical issues emerge. Consider whether a maintained alternative exists or if you can implement MMS support without this library.
🤖 Prompt for AI Agents