fayazara

onelink: Create Link-in-Bio Pages Stored in the URL

Onelink is an experimental link-in-bio web app built with Vue and Nuxt 3. It encodes profile details and links into a Base64 URL parameter, so a profile can be shared without a separate data store; the URL can become long.

Stars
1k
Forks
225
Stars, last 30 days
+5
Last commit
1.4 years ago
Contributors
2

Our take

Inactiveno commits in over a year

Health score

19/100

How it is scored
Activity
19
Community
17
Issues
21
Pull requests
20

+5 stars in the last 30 days

  • Fewer contributors than 86% of the projects we track

Onelink is a focused URL-backed profile experiment, but its inactive maintenance and highly concentrated contributions make it a cautious choice for anything that needs ongoing support.

Good fit if

  • You want to explore a link-in-bio page where profile data travels in the URL.
  • You are comfortable working with a Vue and Nuxt 3 app and Node.js runtime.
  • You can accept the MIT license and maintain or adapt the project yourself.

Look elsewhere if

  • Your profiles need short, stable links without relying on a link-shortening service.
  • You need active maintenance: there have been no commits in over a year and no releases in the past year.
  • You need evidence of broad contributor support or recent issue and pull-request handling. Most of the code comes from one person, and none were recorded recently.
All health signals
Last commit2025-05-22 (1.4 years ago)
Commits, last 90 days0
Releases, last 12 months0
Contributors2 (top contributor: 92% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age3 years

Checked on 2026-10-30 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

1,032

Forks

224

Change since Nov 17, 2026: 0 stars·0 forks

Overview

Onelink is an experimental link-in-bio web app built with Vue and Nuxt 3. It puts profile data in a Base64-encoded URL query parameter rather than relying on a separate data store, giving people a way to share a profile through a link.

The example profile includes a name, description, image, social and contact links, and a list of custom links. This approach suits small personal profiles where carrying the data in the URL is acceptable, but the encoded payload can make links unwieldy.

Key Features

  • Encodes profile data as a Base64 string in a URL query parameter.
  • Displays profile details including a name, description, and image URL.
  • Supports social and contact destinations such as email, phone, and social profiles.
  • Includes a list of custom links with labels, destinations, and icon identifiers.
  • Uses a path segment for the page template, with templates identified as a roadmap item.

Use Cases

  • An individual can share a compact landing page for social and contact links.
  • A creator can put custom destinations, such as a website or course, behind one profile link.
  • A small project can prototype a link-in-bio experience without setting up a database.

What you need

Detected in the repository

  • Node.js (from package.json)

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Install dependencies and start the development server:

npm install
npm run dev

See the repository README for other package managers, production builds, and deployment details.

Considerations

  • The Base64-encoded profile is carried in the query string, so richer profiles can create very long URLs. The README suggests using a link shortener.
  • The README lists templates and code refactoring as roadmap items, so multiple finished templates and a polished codebase should not be assumed.
  • The repository is marked inactive, with no recent commits or releases. Contribution and activity measurements also show that work is concentrated in one contributor.
  • The supplied requirements list Node.js; it does not list tests or CI, so no automated test or build-validation setup is indicated by the available data.

Found this useful?

Share it with someone who would like onelink.