Download the PHP package waaseyaa/framework without Composer
On this page you can find all versions of the php package waaseyaa/framework. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download waaseyaa/framework
More information about waaseyaa/framework
Files in waaseyaa/framework
Package framework
Short Description Waaseyaa monorepo — a modern, entity-first, AI-native CMS
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package framework
Waaseyaa
A PHP framework for content-driven websites and applications, built around entities, explicit access policies, and reusable Symfony components.
Define your content model once, then compose storage, validation, APIs, editorial workflows and presentation around it. Waaseyaa brings a Drupal-inspired entity and field model to Composer packages without a Drupal runtime dependency. Applications own their domain, branding and deployment.
Status: alpha. Contracts can change, and package convergence is ongoing. The candidate production profile is a single application node with local SQLite. S1 consumer certification is still pending. Start with the support contract and stability policy when evaluating adoption.
Documentation · Releases · Roadmap · Report a bug
What you can build
Waaseyaa is intended for websites and applications that need structured content, application accounts, access rules and editorial workflows, with a custom user experience. It supplies the reusable framework beneath Waaseyaa Studio and can also be used independently of a builder or hosted service.
| Capability | Where to start |
|---|---|
| Content entities, typed fields and persistence | Entity system |
| Entity and field access policies | Access control |
| Content lifecycle and editorial transitions | Workflows |
| JSON:API, with optional GraphQL integration | GraphQL |
| Declarative listings and server-rendered pages | SSR |
| Page documents and a shared editor contract | Page builder |
| Agent tools and local development integrations | Bimaaji |
These are composable capabilities with their own contracts and qualification limits. A package's presence does not certify every combination or application journey. Package audit coverage tracks assessment separately from remediation.
Start an application
Use the application skeleton, waaseyaa/waaseyaa. This repository contains the
framework and its packages; it is not the application template.
You need PHP 8.5 with pdo_sqlite, sqlite3 and sodium, Composer on the
feature line in the support contract, and
SQLite 3.40 or newer within the 3.x line. Composer checks the installed package
requirements. Node.js 24 is needed when building or testing the Admin SPA.
Follow the initialization prompts, then open http://127.0.0.1:8080.
site:init generates the site contract; install:init materializes schema and
activates configuration. Verification checks the generated contract and
acceptance tests. The development command serves with FrankenPHP; its setup
and platform requirements are covered in the
skeleton guide.
Next, read application anatomy and ownership to find where providers, routes, entities, templates and application policies belong. The skeleton guide covers the full lifecycle and site contract explains generated ownership. For native Windows and Linux entrypoints, see native host support.
Choose your package set
For an existing Composer project, the curated metapackages provide different starting points. Follow their manifests for the exact dependency closure.
| Package | Scope |
|---|---|
waaseyaa/core |
Entity, field, storage, configuration, access and foundational services |
waaseyaa/cms |
Core plus content types, page building, workflows, JSON:API, SSR and CLI |
waaseyaa/full |
CMS plus search, relationships, attachments, structured import and selected AI tooling |
waaseyaa/ai-development |
Local AI development and testing tools; install under require-dev only |
full does not mean every package. Opt-in domains such as messaging and groups
are separate choices. The skeleton requires the root waaseyaa/framework
aggregate; its production closure also keeps opt-in domains separate. See the
package architecture decision and
development-plane boundary.
How the framework fits together
Packages are organized into seven layers: Foundation, Core Data, Content Types, Services, API, AI and Interfaces. Layer checks constrain dependencies, with explicitly tracked exceptions and existing cycles. The current architecture map lists ownership and enforcement.
Symfony supplies maintained infrastructure such as HTTP messages, routing, console commands, events and validation. Waaseyaa owns its content model, authorization policy and lifecycle contracts. The infrastructure reuse policy requires evaluating Symfony before maintaining a custom equivalent.
Application behavior is composed through providers and the framework's entity repository pipeline. Use those extension points rather than copying framework internals into an application. Start with package discovery and the extension SDK.
Studio composes these capabilities into a builder experience. Framework remains usable independently; product boundaries explain that division and the acceptance work still outstanding.
Support and upgrades
The S1 support contract defines the candidate
production topology, tested toolchain and limits. S1 uses one application node
and one authoritative SQLite database on a local filesystem. Invalid database
DSN, URI, UNC and device paths are refused with S1-DB001; production also
refuses in-memory databases. See the SQLite topology.
H1 (multi-node serving), MySQL/PostgreSQL, shared/network database filesystems, WebKit/Safari and unlisted web runtimes are unsupported. Development-runtime availability is not production certification.
Alpha fixes ship forward in new releases. Review the changelog, upgrade guidance and stability charter before changing versions.
Contribute
Start with AGENTS.md, the operating contract and design-first workflow. Substantive changes use a portable change record, an explicit intended contract, focused acceptance evidence and review. Search existing issues and specs before opening overlapping work.
That test command is a focused starting point, not whole-framework
qualification. Follow the local testing policy
for checks appropriate to your change and host. Repository maintainer skills
live in .agents/skills/.
Report vulnerabilities through SECURITY.md. Project stewardship and continuity are described in MAINTAINERS.md and SUCCESSION.md.
License
GPL-2.0-or-later.
See the roadmap for convergence priorities and planned shared social capabilities, including posts, comments and conversations. Planned scope is not a claim of released functionality.
All versions of framework with dependencies
ext-pdo_sqlite Version *
ext-sodium Version *
ext-sqlite3 Version *
dragonmantank/cron-expression Version ^3.0
symfony/console Version ^8.0
symfony/dotenv Version ^8.0
symfony/html-sanitizer Version ^8.0
waaseyaa/access Version self.version
waaseyaa/admin-surface Version self.version
waaseyaa/ai-pipeline Version self.version
waaseyaa/ai-schema Version self.version
waaseyaa/ai-tools Version self.version
waaseyaa/analytics Version self.version
waaseyaa/api Version self.version
waaseyaa/attachment Version self.version
waaseyaa/auth Version self.version
waaseyaa/billing Version self.version
waaseyaa/bimaaji Version self.version
waaseyaa/cache Version self.version
waaseyaa/cli Version self.version
waaseyaa/config Version self.version
waaseyaa/database-legacy Version self.version
waaseyaa/debug Version self.version
waaseyaa/deployer Version self.version
waaseyaa/entity Version self.version
waaseyaa/entity-storage Version self.version
waaseyaa/error-handler Version self.version
waaseyaa/field Version self.version
waaseyaa/foundation Version self.version
waaseyaa/frankenphp Version self.version
waaseyaa/geo Version self.version
waaseyaa/github Version self.version
waaseyaa/graphql Version self.version
waaseyaa/groups Version self.version
waaseyaa/http-client Version self.version
waaseyaa/i18n Version self.version
waaseyaa/inertia Version self.version
waaseyaa/ingestion Version self.version
waaseyaa/listing Version self.version
waaseyaa/mail Version self.version
waaseyaa/media Version self.version
waaseyaa/menu Version self.version
waaseyaa/mercure Version self.version
waaseyaa/migration Version self.version
waaseyaa/node Version self.version
waaseyaa/note Version self.version
waaseyaa/notification Version self.version
waaseyaa/oauth-provider Version self.version
waaseyaa/page-builder Version self.version
waaseyaa/path Version self.version
waaseyaa/plugin Version self.version
waaseyaa/publishing Version self.version
waaseyaa/queue Version self.version
waaseyaa/relationship Version self.version
waaseyaa/routing Version self.version
waaseyaa/scheduler Version self.version
waaseyaa/search Version self.version
waaseyaa/seo Version self.version
waaseyaa/site-contract Version self.version
waaseyaa/ssr Version self.version
waaseyaa/state Version self.version
waaseyaa/structured-import Version self.version
waaseyaa/taxonomy Version self.version
waaseyaa/telescope Version self.version
waaseyaa/typed-data Version self.version
waaseyaa/user Version self.version
waaseyaa/validation Version self.version
waaseyaa/workflows Version self.version