v1.0.19
KO

OPEN SOURCE · APACHE-2.0

Start free.
Build with freedom.

Verify before adoption. Stay in control after.

All source code, tests, and automated release workflows are transparently open. Build, modify, and operate freely under the Apache-2.0 license.

View source on GitHub Read the license

OPEN BY EVIDENCE

Visible trust.

Trace implementation, verification, release, and product boundaries in the public project.

01SOURCEInspect Implementation DirectlyInspect the React and TypeScript source that ships in the package.beautiful-grid/02TESTSInspect the quality gatesSee how unit, consumer, bundle-budget, and end-to-end checks run..github/workflows/tests.yml03RELEASETrace the release processFollow the public path from version tag to verification, build, and npm publish..github/workflows/publish-npm.yml04PRODUCT FACTSReview scope and limitsCheck runtime support, strengths, and unsuitable use cases before adoption./en/product-facts

OUR POSITION

Open principles.

We measure open source by the adopter’s ability to verify and choose—not by the size of a contributor community.

01Verifiable trust

Proven by code, not words.

Implementation, tests, and support boundaries are public, so adoption can be based on evidence rather than claims.

Review test workflow
02Lasting control

Control stays with the adopter.

Build and modify the public source in a standard React and TypeScript environment, then choose how to operate it.

Inspect library source
03Honest boundaries

Honest about capabilities and limits.

We do not inflate community size or future plans. We describe what can be verified in the current release.

Review product facts

FREEDOM WITHOUT DEPENDENCY

Freedom that lasts.

BeautifulGrid runs inside your existing React application. Public source and a standard toolchain let you decide how to build, modify, and update it.

Review installation and setup
  1. 01
    Build it yourself

    Build the package from public source with a standard toolchain.

  2. 02
    Modify it yourself

    Adapt or extend the implementation and styles for your project.

  3. 03
    Operate it yourself

    Run it inside your React application without a required hosted service.

  4. 04
    Choose when to update

    Review versions and changes, then update on your project schedule.

PRACTICAL LICENSE GUIDE

Freedom, defined.

A practical view of Apache-2.0 permissions, redistribution duties, and trademark boundaries.

01YOU MAY

Permissions

  • Commercial use by individuals and companies
  • Modification and derivative work
  • Redistribution of original or modified versions
  • Operate a fork under a distinct identity
02WHEN YOU REDISTRIBUTE

Redistribution duties

  • Preserve a copy of the Apache-2.0 license
  • Preserve copyright and NOTICE statements
  • Mark files that you changed
  • Include applicable notices with the distribution
03BRAND BOUNDARY

Trademark boundary

  • The source license does not grant trademark rights
  • Do not imply an official relationship or endorsement
  • Forks should use a distinct name and visual identity
  • Truthful compatibility and usage statements are allowed
LICENSEApache-2.0 termsNOTICECopyright noticesTRADEMARKName and brand policy

This summary is provided for clarity and is not legal advice. The LICENSE terms govern actual use and redistribution.

BUILT IN PUBLIC

An open process.

The repository shows how the package is tested, how releases are published, and which problems are known. Openness is not a demand for participation; it is a commitment to verifiability.

Test workflow Release workflow Known issues

VERIFY. DECIDE. OPERATE.

The choice is yours.

Use the real source and your own data to decide whether BeautifulGrid fits.

Get started in 5 minutes Inspect the source Support and limits
Project resourcesReport an issue ↗Security policy ↗Contributing guide ↗Report vulnerabilities through the private process in the security policy, not a public issue.