PODSHL PublishRegister ProjectsLog SecurityNotice

Imprint Impressum

Responsible


  

Contact

Written out rather than linked. An imprint has to be published; it does not have to be published to an address harvester, and a person reads it either way.

Reporting a security finding

Notices about content we mirror

We mirror files that open-source projects publish in their own repositories. A notice reaches the mirror, never the source: the copy here is withdrawn and the project returns to unknown — the state of one that never registered — while everything in the developer's repository is untouched.

Every removal is logged with a public reason code, and the affected party is told why. That log entry is the statement of reasons. A notice aimed at a problem class rather than at a specific project is refused, because otherwise naming somebody else's software could be forbidden by whoever owns the name.

File a notice ·

No warranty

This service and the client are provided as is and without warranty of any kind, express or implied — including any warranty of merchantability, fitness for a particular purpose, accuracy, or uninterrupted availability. Use is at your own risk.

Support content is written by the projects themselves, not by us. We mirror what a project publishes in its own repository and serve a copy. We do not author it, we do not review it for correctness, and we do not endorse it. A solution that is wrong is wrong at its source, and the project that published it is named in every answer so you can see whose advice you are taking.

What the client changes on a machine, it changes because a person said yes. Every action is shown first, dry-run first, reversible, and consented to individually. That is a bound on effect, not a guarantee of outcome: nothing here promises that a suggested change fixes anything, and you remain responsible for what you run on your own systems. Back up what matters before acting on any advice, from here or anywhere.

To the fullest extent permitted by law the operator is not liable for any damage arising from use of this service, the client, or any content mirrored here. Liability for intent and gross negligence, and liability under mandatory law — including injury to life, body or health, and the German Product Liability Act — is unaffected, because it cannot be excluded and a notice pretending otherwise would be worthless.

The licences say this too, in their own words: AGPL-3.0 sections 15 and 16 for the code, Apache-2.0 sections 7 and 8 for the specification. This is the same statement in a place somebody will actually read.

Links to other sites

Project pages, repositories and the addresses in a published manifest belong to the projects that published them. We do not control what is at the other end and are not responsible for it. Anchors are re-checked on a schedule and what we observe is stated as an observation — never as a verdict about anybody.