Enroll freenet-core

[sanity]

Enrol projects/freenet-core

I have verified each of the following before submitting this project (tick each box by changing [ ] to [x]):

• I am a core maintainer of this project.
• I accept the OSS Scanner terms.
• I confirm that I believe my project meets the inclusion criteria and is an established project that users depend on.
• project.yaml follows the README (one project per PR; tools/validate.py passes locally).
• tools/check <name> builds the project, and its tests run in the shell that follows.
• primary_contact must be the email address of the primary security contact.
• There is a Dockerfile that builds the project (required) in one of two places: in the project's repository at the path dockerfile: names, or next to project.yaml in this repo.
• threat_model.md is written for this project (recommended but optional), placed in the same way: in the repository at the path threat_model: names, or next to project.yaml in this repo.

Context: freenet-core is the reference node for Freenet, a peer-to-peer platform for decentralized applications. Every node accepts UDP traffic from arbitrary peers, compiles and runs WebAssembly contract code received from the network in a wasmtime sandbox, holds users' private keys in delegates, and serves web apps and a client API to the local browser. It has been developed since 2021, ships releases several times a week, and auto-updates its installed nodes.

• License: AGPL-3.0. LICENSE.md opens with a plain-language explanation, so GitHub cannot classify it.
• Security contact: ian@freenet.org. SECURITY.md routes reports through GitHub private advisories, which is why it lists no email address.
• Build check: tools/check --no-shell freenet-core builds the image, and 7861 of 7866 tests pass in it. The 5 failures expect permission-denied file errors, which never occur when the tests run as root.
• One test binary is excluded: freenet-ping-app's tests link two freenet-stdlib versions, which current linkers reject. That's tracked in build: freenet-test-network pulls in freenet-stdlib 0.1.x, so test binaries link two stdlib copies (duplicate symbol under rust-lld and mold 2.37) freenet/freenet-core#5950.

https://claude.ai/code/session_0181pVxHYnAX2coR93KzndWg

[AI-assisted - Claude]

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[github-actions]

Enrolment triage: projects/freenet-core

Repository: freenet/freenet-core at main · opened by sanity

	Check	Result
✅	Repository	created 5 years ago, last push today
ℹ️	Stars / forks	3,110 stars · 193 forks · 45 watching
⚠️	Outside participants	2 people from outside the project opened 3 of the last 100 issues and pull requests
ℹ️	Criticality score	0.67 on the OpenSSF scale of 0 to 1 signals created_since 64, updated_since 0, contributor_count 53, org_count 5, commit_frequency 47.3, recent_releases_count 100, closed_issues_count 530, updated_issues_count 539, comment_frequency 4.3, dependents_count 97
ℹ️	Package rank	by downloads: nothing from this repository found in the top 15,000 on PyPI or the top 10,000 on npm or the top 1,000 on crates.io
⚠️	License	GitHub cannot name the license; its file says # How Freenet Licensing Works
✅	Opened by an active maintainer	collaborator on the repository; 100+ commits in the last 12 months; #1 contributor
ℹ️	Contact in SECURITY.md	SECURITY.md gives no email address to check ian@freenet.org against
ℹ️	OSS-Fuzz	not found in OSS-Fuzz
ℹ️	.oss-scanner/ in the repository	not present; the Dockerfile is in this pull request
✅	Pull request scope	only this project's directory
✅	tools/validate.py	passes
⚠️	Checklist	2 of 8 not ticked: I accept the [OSS Scanner terms](https://red.anthropic.com/oss-scanner/terms/).; I confirm that I believe my project meets the inclusion criteria and is an estab…

_{Automated, from public data, to help reviewers. Enrolment is decided case by case against the criteria. If you think we got something wrong, please tell us in a reply.}