Repository navigation
|
How can a team catch Sensitive session details stored in sessionStorage without protection automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'sessionStorage.setItem\|sessionStorage' --include='*.js' --include='*.ts' --include='*.html' . && ! grep -rn 'encryptedSession\|clearSessionStorage' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Storing raw authentication or session keys in sessionStorage without encryption or clean-up logic. The fix. Limit and secure the data written to sessionStorage, apply encryption, and ensure data is deleted at session end. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
WEB-SESSION-STORAGEwith a coverage line and a proper exit code.What the hit means. Storing raw authentication or session keys in sessionStorage without encryption or clean-up logic.
The fix. Limit and secure the data written to s…