Gathering detailed insights and metrics for piral-core
Gathering detailed insights and metrics for piral-core
Gathering detailed insights and metrics for piral-core
Gathering detailed insights and metrics for piral-core
piral-ext
Set of standard plugins with component definitions for extending piral-core.
@pidoc/core
Tools for generating a dynamic documentation experience like for docs.piral.io.
@procaaso/pc-piral-instance
Example project illustrating the use of the piral-core and piral-cli packages.
poc-shell
Example project illustrating the use of the piral-core and piral-cli packages.
🚀 Framework for next generation web apps using micro frontends. ⭐️ Star to support our work!
npm install piral-core
Typescript
Module System
Node Version
NPM Version
83.5
Supply Chain
89
Quality
95.3
Maintenance
100
Vulnerability
100
License
TypeScript (94.29%)
JavaScript (3.59%)
SCSS (1.93%)
HTML (0.18%)
CSS (0.01%)
Total Downloads
1,067,891
Last Day
295
Last Week
5,027
Last Month
22,658
Last Year
253,616
MIT License
1,799 Stars
3,903 Commits
132 Forks
31 Watchers
5 Branches
44 Contributors
Updated on May 30, 2025
Minified
Minified + Gzipped
Latest Version
1.8.5
Package Id
piral-core@1.8.5
Unpacked Size
759.04 kB
Size
143.85 kB
File Count
457
NPM Version
lerna/8.1.9/node@v20.12.2+x64 (linux)
Node Version
20.12.2
Published on
Apr 15, 2025
Cumulative downloads
Total Downloads
Last Day
-13.2%
295
Compared to previous day
Last Week
-0.8%
5,027
Compared to previous week
Last Month
-14.5%
22,658
Compared to previous month
Last Year
21.8%
253,616
Compared to previous year
Easily build a next generation web application using microfrontends. Piral enables you to create a modular frontend application that is extended at runtime with decoupled modules called pilets leveraging a microfrontend architecture.
A pilet can be developed independently and ships with the necessary code, as well as all other relevant assets. Pilets are as independent of the host application as you want them to be - making them transferrable between different applications.
This makes Piral an ideal foundation for a mid-sized to large-scale applications developed by distributed teams.
:zap: A pilet is capable of dynamically extending other pilets or using such extension slots itself.
:zap: A pilet can provide or use shared dependencies from other pilets.
:zap: A pilet is isolated (developed and handled) and will never destroy your application.
:zap: A pilet can be developed with any technology using a standard IDE.
:zap: A pilet can be updated and published within seconds.
:zap: A pilet can be rolled out or disabled dynamically to create self-forming applications.
:zap: A pilet can be debugged seamlessly just as if you write a monolith.
Piral itself is developed as a monorepo. As such this repository may contain an overwhelming amount of information.
Our recommendation is to start at the documentation available at docs.piral.io. Working through the available tutorials will give you the necessary information in the best possible order.
While the GitHub issues may be used in case of questions, we would prefer general usage questions to be raised either in our Discord server or at StackOverflow.
Be sure to check our FAQ and the official tutorials upfront!
The main purpose of this repository is to continue to evolve Piral and its core ecosystem, making it faster, more powerful, and easier to use. Development of Piral happens in the open on GitHub, and we are grateful to the community for contributing bugfixes, ideas, and improvements.
Read below to learn how you can take part in improving Piral.
docs
contains the (user) documentationsrc
has the sources for all the developed packages, samples, and pagestest
contains the test setup and (in the future) system teststools
has some of the internal tooling for building the different componentsEach subdirectory contains another README.md
with more information regarding the contents of the specific folder.
We adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.
Read our contributing guide to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to Piral.
To help you get your feet wet and get you familiar with our contribution process, we have a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started.
Piral is released using the MIT license. For more information see the license file.
No vulnerabilities found.
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
SAST tool is run on all commits
Details
Reason
Found 3/13 approved changesets -- score normalized to 2
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
19 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-05-26
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More