Gathering detailed insights and metrics for @angular-architects/module-federation
Gathering detailed insights and metrics for @angular-architects/module-federation
Installations
npm install @angular-architects/module-federationDeveloper
angular-architects
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
Typescript Support
Yes
Node Version
20.17.0
NPM Version
10.8.2
Statistics
736 Stars
298 Commits
203 Forks
32 Watching
12 Branches
20 Contributors
Updated on 27 Nov 2024
Bundle Size
13.74 kB
Minified
4.53 kB
Minified + Gzipped
Languages
TypeScript (93.11%)
JavaScript (5.66%)
CSS (0.73%)
HTML (0.45%)
Shell (0.03%)
Batchfile (0.01%)
Total Downloads
Cumulative downloads
Total Downloads
12,459,456
Last day
0.7%
25,364
Compared to previous day
Last week
2.8%
124,604
Compared to previous week
Last month
2.4%
525,601
Compared to previous month
Last year
29.8%
5,784,185
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Versions
@angular-architects/module-federation
Local Development
Playground App
You can test directly the libraries by using the playground application:
- Start the
hostapplication:1npx nx run playground:serve - Start the
remoteapplication:1npx nx run mfe1:serve --port 3001
By using that approach you can test your modifications on the libraries.
Test Library on external repository
If you want to test the modifications directly on your application, you can follow the steps:
- Start the local registry Verdaccio:
1npx nx run local-registry - Then you can publish the libraries by using:
-
For Module federation:
1npm run publish-local:mf -
For Native federation:
1npm run publish-local:nfThis will first
buildthe libraries andpublishthem to http://localhost:4873
- Then just re-run the
installon the other repo with you favorite package manager.
By default, the version from the package.json will be used. However, you can provide the version for a specific library by using:
1npx nx run native-federation:publish-local -- --ver=17.0.8
Publish Libraries
Follow these steps to publish all libraries on npm:
- For Module federation:
1npm run publish:mf - For Native federation:
This will first1npm run publish:nfbuildthe libraries andpublishthem tonpm registry.
By default, the version from the package.json will be used and the tag will be next. However, you can provide the version and the tag for a specific library by using:
1npx nx run native-federation:publish -- --ver=17.0.8 --tag=latest
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
GitHub workflow tokens follow principle of least privilege
Details
- Info: topLevel 'actions' permission set to 'read': .github/workflows/ci.yml:10
- Info: topLevel 'contents' permission set to 'read': .github/workflows/ci.yml:11
- Info: no jobLevel write permissions found
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
6 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 9
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/angular-architects/module-federation-plugin/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/angular-architects/module-federation-plugin/ci.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/angular-architects/module-federation-plugin/ci.yml/main?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 1 out of 1 npmCommand dependencies pinned
Reason
Found 4/26 approved changesets -- score normalized to 1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 8 are checked with a SAST tool
Reason
18 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-8hc4-vh64-cxmj
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-ghr5-ch3p-vcr6
- Warn: Project is vulnerable to: GHSA-rv95-896h-c2vc
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986 / GHSA-64vr-g452-qvp3
- Warn: Project is vulnerable to: GHSA-9cwx-2883-4wfx
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Score
4.6
/10
Last Scanned on 2024-11-25
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