Initial commit on Forgejo
Fresh repository history for elektrine/tarakan hosted at https://git.elektrine.com/elektrine/tarakan.
This commit is contained in:
commit
af6077b9c3
455 changed files with 78366 additions and 0 deletions
66
lib/tarakan_web/live/page_live/content.html.heex
Normal file
66
lib/tarakan_web/live/page_live/content.html.heex
Normal file
|
|
@ -0,0 +1,66 @@
|
|||
<Layouts.app flash={@flash} current_scope={@current_scope} current_path={assigns[:current_path]}>
|
||||
<Layouts.page width={:focused} class="space-y-8">
|
||||
<header>
|
||||
<h1 class="font-display text-3xl font-medium uppercase leading-[1.05] tracking-[0.02em] text-ink sm:text-4xl">
|
||||
Content policy
|
||||
</h1>
|
||||
<p class="mt-4 max-w-xl text-sm leading-6 text-ink-muted">
|
||||
The public record exists so defenders can reproduce and fix vulnerabilities. Content
|
||||
that serves offense instead of defense is removed.
|
||||
</p>
|
||||
</header>
|
||||
|
||||
<section id="allowed-content" class="border-t-2 border-strong pt-6">
|
||||
<h2 class="font-display text-sm uppercase tracking-[0.12em] text-ink">
|
||||
Allowed content
|
||||
</h2>
|
||||
<ul class="mt-3 max-w-xl list-disc space-y-2 pl-5 text-sm leading-6 text-ink-muted">
|
||||
<li>Security findings pinned to an exact commit of a public repository.</li>
|
||||
<li>
|
||||
Reproduction steps, proof-of-concept snippets, and supporting evidence that let a
|
||||
maintainer or reviewer confirm the issue.
|
||||
</li>
|
||||
<li>Affected version ranges, CWE/CVE identifiers, and vendor notification dates.</li>
|
||||
<li>Reviewer verdicts and the notes needed to justify them.</li>
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<section id="prohibited-content" class="border-t-2 border-strong pt-6">
|
||||
<h2 class="font-display text-sm uppercase tracking-[0.12em] text-ink">
|
||||
Prohibited content
|
||||
</h2>
|
||||
<ul class="mt-3 max-w-xl list-disc space-y-2 pl-5 text-sm leading-6 text-ink-muted">
|
||||
<li>
|
||||
Weaponized malware, droppers, or turnkey exploit kits. A minimal PoC that
|
||||
demonstrates a finding is fine; tooling built to deploy harm is not.
|
||||
</li>
|
||||
<li>
|
||||
Exfiltrated data: personal data, customer records, or anything taken from a system
|
||||
without authorization.
|
||||
</li>
|
||||
<li>
|
||||
Secrets and credentials - API keys, tokens, private keys, passwords. Submissions
|
||||
are automatically scanned for secrets at publish time; findings containing them are
|
||||
blocked or restricted and the exposed credential should be rotated immediately.
|
||||
</li>
|
||||
</ul>
|
||||
</section>
|
||||
|
||||
<section id="takedown-appeals" class="border-t-2 border-strong pt-6">
|
||||
<h2 class="font-display text-sm uppercase tracking-[0.12em] text-ink">
|
||||
Takedowns and appeals
|
||||
</h2>
|
||||
<p class="mt-3 max-w-xl text-sm leading-6 text-ink-muted">
|
||||
Anyone can report content from an account via the <.link
|
||||
navigate={~p"/moderation/report"}
|
||||
class="text-signal hover:underline"
|
||||
>
|
||||
moderation report form
|
||||
</.link>. Moderators may restrict a review or quarantine a repository; every takedown
|
||||
records a reason. If your content was restricted and you believe the decision was
|
||||
wrong, reply on the moderation case or file a new report referencing it - appeals are
|
||||
reviewed by a moderator who did not take the original action.
|
||||
</p>
|
||||
</section>
|
||||
</Layouts.page>
|
||||
</Layouts.app>
|
||||
Loading…
Add table
Add a link
Reference in a new issue