Gathering detailed insights and metrics for @utrecht/web-component-library-angular
Gathering detailed insights and metrics for @utrecht/web-component-library-angular
Gathering detailed insights and metrics for @utrecht/web-component-library-angular
Gathering detailed insights and metrics for @utrecht/web-component-library-angular
Work in Progress: Utrecht Design System based on the NL Design System architecture. Storybook: https://nl-design-system.github.io/utrecht/storybook/
npm install @utrecht/web-component-library-angular
Typescript
Module System
Node Version
NPM Version
78.5
Supply Chain
91.1
Quality
82.1
Maintenance
100
Vulnerability
93.6
License
@utrecht/component-library-css@7.3.0
Updated on Jun 18, 2025
@utrecht/design-tokens@3.3.0
Updated on Jun 18, 2025
@utrecht/tooltip-react@1.0.0
Updated on Jun 18, 2025
@utrecht/tooltip-css@1.0.0
Updated on Jun 18, 2025
@utrecht/component-library-vue@2.3.1
Updated on Jun 16, 2025
@utrecht/design-tokens@3.2.0
Updated on May 27, 2025
TypeScript (73.02%)
SCSS (12.42%)
HTML (5.82%)
JavaScript (4.42%)
MDX (2.33%)
CSS (1.14%)
Vue (0.84%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
EUPL-1.2 License
29 Stars
3,715 Commits
23 Forks
7 Watchers
258 Branches
48 Contributors
Updated on Jun 28, 2025
Latest Version
2.1.0
Package Id
@utrecht/web-component-library-angular@2.1.0
Unpacked Size
2.82 MB
Size
170.61 kB
File Count
29
NPM Version
10.8.3
Node Version
22.9.0
Published on
Oct 06, 2024
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
1
16
The @utrecht/web-component-library-stencil
package contains the actual implementation of every web component, while the @utrecht/web-component-library-angular
only contains wrapper Angular components to help validate all the templates, and some supporting code to support Angular form bindings. The implementation of each component will be loaded separately and on-demand, so including the entire component library will not slow down your application.
Install both packages to use Angular components in your project:
1npm install --save-dev --save-exact \ 2 @utrecht/web-component-library-angular \ 3 @utrecht/web-component-library-stencil
Include UtrechtWebComponentsModule
in the root NgModule
of your project:
1import { NgModule } from "@angular/core"; 2import { BrowserModule } from "@angular/platform-browser"; 3import { UtrechtWebComponentsModule } from "@utrecht/web-component-library-angular"; 4 5import { AppComponent } from "./app.component"; 6 7@NgModule({ 8 declarations: [AppComponent], 9 imports: [BrowserModule, UtrechtWebComponentsModule], 10 providers: [], 11 bootstrap: [AppComponent], 12}) 13export class AppModule {}
The components are rendered using custom elements, but since we provide a corresponding Angular component for every custom element, you don't need to configure CUSTOM_ELEMENTS_SCHEMA
to make use of any of the components.
To make the custom elements work, you also need to call defineCustomElements()
once in your page, immediately when it is loaded. Add this to main.ts
:
1import { defineCustomElements } from "@utrecht/web-component-library-stencil/loader"; 2 3defineCustomElements();
After this you can use web components in your templates:
1<utrecht-heading level="1">Home</utrecht-heading> 2 3<utrecht-paragraph>Hello world!</utrecht-paragraph>
To use the Utrecht theme for the components, use the utrecht-theme
class name and include the design tokens CSS in your angular.json
:
1{ 2 "projects": { 3 "my-app": { 4 "architect": { 5 "build": { 6 "options": { 7 "styles": ["node_modules/@utrecht/design-tokens/dist/index.css", "src/styles.css"] 8 } 9 } 10 } 11 } 12 } 13}
No vulnerabilities found.
Reason
30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
all changesets reviewed
Reason
license file detected
Details
Reason
no binaries found in the repo
Reason
all dependencies are pinned
Details
Reason
SAST tool is not run on all commits -- score normalized to 5
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
83 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
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