OpenLFCP

Share one task, or a whole section of a note — not your vault. End-to-end encrypted, local-first, open protocol.

Translation pending

ProductivityPython · ShellGitHub @openlfcpOnlineOwner unconfirmed

Visit project GitHub

Have you tried it? One tap is enough. No sign-in needed.

Availability: Online; 30-day uptime 100%
Latest code update: Oct 26; Active repository
Latest version: v0.1.0; OpenLFCP MVP 0.1.0 · Oct 6
Contributors: 1; Forks 0
License: License information
This summarizes common license conditions. Check the repository LICENSE, per-file notices, and additional terms for actual conditions.
Information shown for this project
GitHub auto-detection · main repository license
Apache-2.0
Provided license information ↗
Repository observations do not verify all per-file terms, multiple licenses, or dependencies.
Information at the observation time · Last successful collection Oct 28, 04:04 (Korea time)
Check LICENSE in the repository ↗
Common license comparison
The listed licenses allow commercial use when their conditions are met. Check originals for multiple, custom, or unidentified licenses. Scroll the table horizontally on narrow screens.
Commercial use, modification/redistribution, source obligations, and key conditions of common licenses. Names link to official texts.
License · original Commercial use Modification / redistribution Source obligations Key conditions
MIT ↗ Allowed Allowed No source distribution obligation Keep copyright and permission notices in copies/substantial portions
Apache-2.0 ↗ Allowed Allowed No source distribution obligation Keep license, relevant notices and NOTICE; mark modifications. Includes patent grants and termination on patent litigation
BSD-2-Clause ↗ Allowed Allowed No source distribution obligation Keep copyright, conditions and disclaimers in source or binary documentation/materials
BSD-3-Clause ↗ Allowed Allowed No source distribution obligation BSD-2 terms, plus no use of copyright holder/contributor names for endorsement without permission
ISC ↗ Allowed Allowed No source distribution obligation Keep copyright and permission notices in all copies
GPL-2.0 ↗ Allowed Allowed under GPL terms Provide corresponding source for the program/derivatives when distributing Distribute under GPL; keep copyright, license and change notices. Mere aggregation is excluded
GPL-3.0 ↗ Allowed Allowed under GPL terms Provide corresponding source for the program/derivatives when distributing Distribute under GPL; retain notices and mark modifications. Patent terms; provide modified-version installation information for covered consumer products
LGPL-2.1 ↗ Allowed Allowed under LGPL terms Provide source for the library/modifications when distributing the library Apps may link under other licenses; allow library replacement/relinking and reverse engineering to debug modifications
LGPL-3.0 ↗ Allowed Allowed under LGPL terms Provide source for the library/modifications when distributing the library Apps may link under other licenses; ensure replacement, relinking and reverse engineering for debugging modifications; provide installation information for covered products
MPL-2.0 ↗ Allowed Allowed under MPL terms Provide source for MPL-covered files and modifications when distributing Retain MPL and notices at file level; separate files without MPL code may use other licenses
AGPL-3.0 ↗ Allowed Allowed under AGPL terms Provide corresponding source when distributing; offer remote users of modified versions free source access Distribution terms similar to GPL-3.0, plus source-access instructions for network users of modified programs
Unlicense ↗ Allowed Allowed No source distribution obligation Dedicate copyright to the public domain; check the original and limits permitted by law
CC0-1.0 ↗ Allowed Allowed No source distribution obligation Waive copyright and related rights, with fallback permission if ineffective; excludes patents and trademarks
For GPL/LGPL/AGPL, -only permits that version only; -or-later allows that or a later version. Do not infer later-version permission from a label without a version and suffix. Source obligations apply to recipients/users under the terms and do not always require publishing to the entire internet.
GitHub license detection and display guide ↗; GitHub auto-detection · Previous observation · Collected Oct 28
Listed on nomorevibe: Oct 20; Repository created October 2026

Languages

Python 96.9%
Shell 3.1%

Updates1 in the last 30 days

All

Oct 6OpenLFCP MVP 0.1.0GitHub release ↗

Comments

Newest first

···

GitHub issue delivery settings

Checking sign-in status.

Loading comments.

OpenLFCP

Share one task, or a whole section of a note — not your vault. End-to-end encrypted, local-first, open protocol.

Translation pending

ProductivityPython · ShellGitHub @openlfcpOnlineOwner unconfirmed

Visit project GitHub

Have you tried it? One tap is enough. No sign-in needed.

Availability: Online; 30-day uptime 100%
Latest code update: Oct 26; Active repository
Latest version: v0.1.0; OpenLFCP MVP 0.1.0 · Oct 6
Contributors: 1; Forks 0
License: License information
This summarizes common license conditions. Check the repository LICENSE, per-file notices, and additional terms for actual conditions.
Information shown for this project
GitHub auto-detection · main repository license
Apache-2.0
Provided license information ↗
Repository observations do not verify all per-file terms, multiple licenses, or dependencies.
Information at the observation time · Last successful collection Oct 28, 04:04 (Korea time)
Check LICENSE in the repository ↗
Common license comparison
The listed licenses allow commercial use when their conditions are met. Check originals for multiple, custom, or unidentified licenses. Scroll the table horizontally on narrow screens.
Commercial use, modification/redistribution, source obligations, and key conditions of common licenses. Names link to official texts.
License · original Commercial use Modification / redistribution Source obligations Key conditions
MIT ↗ Allowed Allowed No source distribution obligation Keep copyright and permission notices in copies/substantial portions
Apache-2.0 ↗ Allowed Allowed No source distribution obligation Keep license, relevant notices and NOTICE; mark modifications. Includes patent grants and termination on patent litigation
BSD-2-Clause ↗ Allowed Allowed No source distribution obligation Keep copyright, conditions and disclaimers in source or binary documentation/materials
BSD-3-Clause ↗ Allowed Allowed No source distribution obligation BSD-2 terms, plus no use of copyright holder/contributor names for endorsement without permission
ISC ↗ Allowed Allowed No source distribution obligation Keep copyright and permission notices in all copies
GPL-2.0 ↗ Allowed Allowed under GPL terms Provide corresponding source for the program/derivatives when distributing Distribute under GPL; keep copyright, license and change notices. Mere aggregation is excluded
GPL-3.0 ↗ Allowed Allowed under GPL terms Provide corresponding source for the program/derivatives when distributing Distribute under GPL; retain notices and mark modifications. Patent terms; provide modified-version installation information for covered consumer products
LGPL-2.1 ↗ Allowed Allowed under LGPL terms Provide source for the library/modifications when distributing the library Apps may link under other licenses; allow library replacement/relinking and reverse engineering to debug modifications
LGPL-3.0 ↗ Allowed Allowed under LGPL terms Provide source for the library/modifications when distributing the library Apps may link under other licenses; ensure replacement, relinking and reverse engineering for debugging modifications; provide installation information for covered products
MPL-2.0 ↗ Allowed Allowed under MPL terms Provide source for MPL-covered files and modifications when distributing Retain MPL and notices at file level; separate files without MPL code may use other licenses
AGPL-3.0 ↗ Allowed Allowed under AGPL terms Provide corresponding source when distributing; offer remote users of modified versions free source access Distribution terms similar to GPL-3.0, plus source-access instructions for network users of modified programs
Unlicense ↗ Allowed Allowed No source distribution obligation Dedicate copyright to the public domain; check the original and limits permitted by law
CC0-1.0 ↗ Allowed Allowed No source distribution obligation Waive copyright and related rights, with fallback permission if ineffective; excludes patents and trademarks
For GPL/LGPL/AGPL, -only permits that version only; -or-later allows that or a later version. Do not infer later-version permission from a label without a version and suffix. Source obligations apply to recipients/users under the terms and do not always require publishing to the entire internet.
GitHub license detection and display guide ↗; GitHub auto-detection · Previous observation · Collected Oct 28
Listed on nomorevibe: Oct 20; Repository created October 2026

Languages

Python 96.9%
Shell 3.1%

Updates1 in the last 30 days

All

Oct 6OpenLFCP MVP 0.1.0GitHub release ↗

Comments

Newest first

···

GitHub issue delivery settings

Checking sign-in status.

Loading comments.

Repository	Purpose
`spec`	Normative specifications, profiles, interoperability vectors, registries, ADR/RFC material
`sdk-ts`	Reusable TypeScript LFCP implementation (no Obsidian dependency)
`sdk-rs`	Independent Rust LFCP implementation
`server`	Application-agnostic reference LFCP server
`obsidian`	Obsidian editor adapter and product UI
`examples`	Small protocol examples and interoperability demonstrations

Document	Purpose
docs/BACKLOG-MVP-0.1.md	Authoritative planning source: MVP 0.1 issue numbers, dependencies and acceptance criteria
docs/MVP-0.1-PROTOCOL-SCOPE.md	Which parts of LFCP Wire the secure MVP requires, and what is deferred
docs/AGENT-OPERATING-GUIDE.md	Source-of-truth hierarchy, repository boundaries and rules for agents and contributors
docs/PROJECT-NARRATIVE.md	Project history, vision and architecture narrative
docs/ARTIFACTS-INDEX.md	Catalog of every current artifact and the repository it lives in
docs/engineering-conventions.md	Branches, commits, validation, labels, versioning and the spec-change process

Repository	Purpose
`spec`	Normative specifications, profiles, interoperability vectors, registries, ADR/RFC material
`sdk-ts`	Reusable TypeScript LFCP implementation (no Obsidian dependency)
`sdk-rs`	Independent Rust LFCP implementation
`server`	Application-agnostic reference LFCP server
`obsidian`	Obsidian editor adapter and product UI
`examples`	Small protocol examples and interoperability demonstrations

Document	Purpose
docs/BACKLOG-MVP-0.1.md	Authoritative planning source: MVP 0.1 issue numbers, dependencies and acceptance criteria
docs/MVP-0.1-PROTOCOL-SCOPE.md	Which parts of LFCP Wire the secure MVP requires, and what is deferred
docs/AGENT-OPERATING-GUIDE.md	Source-of-truth hierarchy, repository boundaries and rules for agents and contributors
docs/PROJECT-NARRATIVE.md	Project history, vision and architecture narrative
docs/ARTIFACTS-INDEX.md	Catalog of every current artifact and the repository it lives in
docs/engineering-conventions.md	Branches, commits, validation, labels, versioning and the spec-change process

OpenLFCP

License information

Information shown for this project

Common license comparison

Languages

Updates1 in the last 30 days

Comments

OpenLFCP

License information

Information shown for this project

Common license comparison

Languages

Updates1 in the last 30 days

Comments

Enlarged image

Do you operate this project?

Introduction

README

openlfcp/.github

Repositories

Project documents

Organization defaults

Validate from a clean checkout

License

README

README

openlfcp/.github

Repositories

Project documents

Organization defaults

Validate from a clean checkout

License

Commercial use, modification/redistribution, source obligations, and key conditions of common licenses. Names link to official texts.
License · original	Commercial use	Modification / redistribution	Source obligations	Key conditions
MIT ↗	Allowed	Allowed	No source distribution obligation	Keep copyright and permission notices in copies/substantial portions
Apache-2.0 ↗	Allowed	Allowed	No source distribution obligation	Keep license, relevant notices and NOTICE; mark modifications. Includes patent grants and termination on patent litigation
BSD-2-Clause ↗	Allowed	Allowed	No source distribution obligation	Keep copyright, conditions and disclaimers in source or binary documentation/materials
BSD-3-Clause ↗	Allowed	Allowed	No source distribution obligation	BSD-2 terms, plus no use of copyright holder/contributor names for endorsement without permission
ISC ↗	Allowed	Allowed	No source distribution obligation	Keep copyright and permission notices in all copies
GPL-2.0 ↗	Allowed	Allowed under GPL terms	Provide corresponding source for the program/derivatives when distributing	Distribute under GPL; keep copyright, license and change notices. Mere aggregation is excluded
GPL-3.0 ↗	Allowed	Allowed under GPL terms	Provide corresponding source for the program/derivatives when distributing	Distribute under GPL; retain notices and mark modifications. Patent terms; provide modified-version installation information for covered consumer products
LGPL-2.1 ↗	Allowed	Allowed under LGPL terms	Provide source for the library/modifications when distributing the library	Apps may link under other licenses; allow library replacement/relinking and reverse engineering to debug modifications
LGPL-3.0 ↗	Allowed	Allowed under LGPL terms	Provide source for the library/modifications when distributing the library	Apps may link under other licenses; ensure replacement, relinking and reverse engineering for debugging modifications; provide installation information for covered products
MPL-2.0 ↗	Allowed	Allowed under MPL terms	Provide source for MPL-covered files and modifications when distributing	Retain MPL and notices at file level; separate files without MPL code may use other licenses
AGPL-3.0 ↗	Allowed	Allowed under AGPL terms	Provide corresponding source when distributing; offer remote users of modified versions free source access	Distribution terms similar to GPL-3.0, plus source-access instructions for network users of modified programs
Unlicense ↗	Allowed	Allowed	No source distribution obligation	Dedicate copyright to the public domain; check the original and limits permitted by law
CC0-1.0 ↗	Allowed	Allowed	No source distribution obligation	Waive copyright and related rights, with fallback permission if ineffective; excludes patents and trademarks

Commercial use, modification/redistribution, source obligations, and key conditions of common licenses. Names link to official texts.
License · original	Commercial use	Modification / redistribution	Source obligations	Key conditions
MIT ↗	Allowed	Allowed	No source distribution obligation	Keep copyright and permission notices in copies/substantial portions
Apache-2.0 ↗	Allowed	Allowed	No source distribution obligation	Keep license, relevant notices and NOTICE; mark modifications. Includes patent grants and termination on patent litigation
BSD-2-Clause ↗	Allowed	Allowed	No source distribution obligation	Keep copyright, conditions and disclaimers in source or binary documentation/materials
BSD-3-Clause ↗	Allowed	Allowed	No source distribution obligation	BSD-2 terms, plus no use of copyright holder/contributor names for endorsement without permission
ISC ↗	Allowed	Allowed	No source distribution obligation	Keep copyright and permission notices in all copies
GPL-2.0 ↗	Allowed	Allowed under GPL terms	Provide corresponding source for the program/derivatives when distributing	Distribute under GPL; keep copyright, license and change notices. Mere aggregation is excluded
GPL-3.0 ↗	Allowed	Allowed under GPL terms	Provide corresponding source for the program/derivatives when distributing	Distribute under GPL; retain notices and mark modifications. Patent terms; provide modified-version installation information for covered consumer products
LGPL-2.1 ↗	Allowed	Allowed under LGPL terms	Provide source for the library/modifications when distributing the library	Apps may link under other licenses; allow library replacement/relinking and reverse engineering to debug modifications
LGPL-3.0 ↗	Allowed	Allowed under LGPL terms	Provide source for the library/modifications when distributing the library	Apps may link under other licenses; ensure replacement, relinking and reverse engineering for debugging modifications; provide installation information for covered products
MPL-2.0 ↗	Allowed	Allowed under MPL terms	Provide source for MPL-covered files and modifications when distributing	Retain MPL and notices at file level; separate files without MPL code may use other licenses
AGPL-3.0 ↗	Allowed	Allowed under AGPL terms	Provide corresponding source when distributing; offer remote users of modified versions free source access	Distribution terms similar to GPL-3.0, plus source-access instructions for network users of modified programs
Unlicense ↗	Allowed	Allowed	No source distribution obligation	Dedicate copyright to the public domain; check the original and limits permitted by law
CC0-1.0 ↗	Allowed	Allowed	No source distribution obligation	Waive copyright and related rights, with fallback permission if ineffective; excludes patents and trademarks

OpenLFCP

Languages

Updates1 in the last 30 days

Comments

Trending in Productivity

OpenLFCP

Languages

Updates1 in the last 30 days

Comments

Trending in Productivity

Do you operate this project?

Introduction

README

openlfcp/.github

Repositories

Project documents

Organization defaults

Validate from a clean checkout

License

README

README

openlfcp/.github

Repositories

Project documents

Organization defaults

Validate from a clean checkout

License