Repository navigation
|
How can a team catch Missing EU GPSR manufacturer info or product safety warning disclosures 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 -rniE 'gpsr|general product safety|product safety|manufacturerInfo|safetyWarning' . 2>/dev/nullRead 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. E-commerce or digital product listing present but missing manufacturer email, postal address, or product safety warnings on the interface. The fix. Provide prominent manufacturer contact details (email and postal address) and any applicable product safety warnings directly on the product listing or online interface for any consumer goods distributed in the EU. 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
BOTH-GPSR-COMPLIANCE-MISSINGwith a coverage line and a proper exit code.What the hit means. E-commerce or digital product listing present but missing manufacturer email, postal address, or product safety warnings on the interface.
The fix. Provide prominent manufacturer contact details (e…