ShipItWorks

Home PocketSec

PocketSec

Find out how hackable you are. The scan runs in your browser; what leaves the device is not yet traced (the password check sends a 5-character hash prefix to Have I Been Pwned).

Scorecard

56/ 100

Stage: Alpha on our own rubric. Google Play: No Android app.

Primary journey: shown with sample data

Scored 2026-11-08 on our own rubric; repository at commit af82be6.

What we promised, and what we have not finished. We promised one public rubric for every product, a list of what is not finished on every page, and a named source for every number. Most of these products are not finished, and each page says where it stops. Read the rubric or every claim and its source.

PocketSec demo · 1:56Captions · Transcript

Recorded 2026-11-08 on the demo profile. The scorecard in the video shows 63; the site shows 56/100 on our own rubric (2026-11-08). The device check on a real device, the breach lookup and the PDF report were not run. The AUTO-5 menu wording is not confirmed on a real Chrome for Android or Android 16. Re-recorded 2026-11-08 against pocketsec main af82be6; shows #88 AUTO-5 menu wording and #65 shorter habit summaries on the demo profile; the unmeasured 'sixty seconds' narration is now attributed to the button label; the changelog gap line is removed. Captions aligned and checked (worst cue 0.05 s); frame scan no hits. Re-encoded 2026-11-08. Voice is AI-generated (ElevenLabs). Shows made-up demo data. Read the transcript.

Email us about PocketSec

This button opens your email app with the subject already filled in. Your message comes to support@shipitworks.com. There is no form and no database. Privacy notice.

Works today

Each line links to the scorecard row that backs it.

Not finished

From the same scorecard, next to the claims.

  1. The web device check (AUTO-1..5), the habits audit (HAB-1..6), the password check and the PDF report have no test or proof log on the main branch; the web test suite and browser run of 2026-11-01 are on a branch that is not merged
  2. Shield Score, the build and the live site are each half credit: a recorded run exists, but no proof log for them is on main
  3. What leaves the device is not yet traced: no network capture is on main; the README on main says a no-transmission claim for the password and the page says '60-Second Security Scan' (not measured)
  4. AUTO-5 menu-path wording changed (#88), but its check script does not pass on Android and no log is committed
  5. No TWA or AAB; assetlinks.json still holds REPLACE_WITH_ placeholders; the Play 12x14 closed-test rule applies
  6. LICENSE.md is PolyForm Noncommercial while the plan says All rights reserved - mismatch unresolved
  7. No CSP header; no privacy page on main; contrast, keyboard and TalkBack not checked; dark theme is fixed with no light mode
  8. Native fix-text Settings paths: 4 of 5 found on a stock Android 36 emulator, 1 not found (Software update), exit 1 (proof/native-fix-paths.log, 2026-11-08T06:14:48Z); not a phone
  9. CHANGELOG.md on main still says there are no release tags (tags v0.1.0 to v0.5.0 exist); package.json says 0.1.0
  10. Web code has no test script in package.json; the only test run on main is the 43 native engine tests, on a Linux JVM, not a phone

What changed

Dated lines from the scorecard. The source code is private, so these lines are the public record.

The next step for PocketSec.

Email us about PocketSec