Four compliance filings with a document for each one

#opensource #security #github #software

Four compliance filings, each with a document behind it. This issue covers tools that turn a compliance question into a report, a clock, a registry finding, or a repair binder.

What this issue covers

These pages turn compliance requirements into documents and recorded findings for the people responsible for acting on them.

PartsProof


	PartsProof helps makers check whether Article 14 reporting applies to products sold or shipped into the EU. Its scope checker asks six questions and returns an in-scope, out-of-scope, or edge-case answer with the obligation dates. The site also generates a software bill of materials from any public GitHub repository. The result is a security document that can be produced without an account.

PolicyDrift


	PolicyDrift loads a site, lists every third-party tracker it contacts, and compares those findings with the privacy policy linked from the page. It marks trackers the policy does not mention. A site owner gets a registry of vendors and findings such as undisclosed trackers, premature claims, overclaimed descriptions, and pages with no policy to read.

TrustDesk


	TrustDesk gives platforms a report form for the federal 48-hour intimate-image removal law. Each report gets a 48-hour clock and a log recording what the platform did and when. The desk also checks whether a request contains the required signature, image location, good-faith statement, and contact information. Platform operators get the request record, the deadline, and the action history together.

TrustDesk gives platforms a report form for the federal 48-hour intimate-image removal law. Each report gets a 48-hour clock and a log recording what the platform did and when. The desk also checks whether a request contains the required signature, image location, good-faith statement, and contact information. Platform operators get the request record, the deadline, and the action history together.

CivicBinder


	CivicBinder checks public entity websites for accessibility problems and turns the findings into a repair binder. Its index tracks public sites and shows when each site was last scanned. A city clerk or accessibility lead gets a report of the findings, the relevant deadline information, and a list of repairs to work through.

One issue a week, and one shipped product taken apart every month. What each product does, what it cost to build, what the pipeline behind it looks like, and what the numbers did, read off the repository and the live site, not written from memory. Join the list.

DEV Community