Gathering detailed insights and metrics for @navikt/personbruker-telefon-input
Gathering detailed insights and metrics for @navikt/personbruker-telefon-input
React komponenter for Arbeidsforhold
Installations
npm install @navikt/personbruker-telefon-inputDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>=8
Node Version
12.8.0
NPM Version
6.10.3
Releases
41
Languages
3
TypeScript
SCSS
HTML
TypeScript (95.56%)
SCSS (3.99%)
HTML (0.45%)
Developer
navikt
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
825 Commits
13 Watchers
2 Branches
26 Contributors
Updated on Jun 23, 2025
Maintainers
12
Package Meta Information
Latest Version
0.0.3-18
Package Id
@navikt/personbruker-telefon-input@0.0.3-18
Unpacked Size
542.37 kB
Size
229.34 kB
File Count
12
NPM Version
6.10.3
Node Version
12.8.0
Total Downloads
Cumulative downloads
Total Downloads
NaN
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
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
11
Dev Dependencies
35
@babel/core@babel/plugin-proposal-class-properties@babel/preset-typescript@svgr/rollup@types/classnames@types/fetch-mock@types/jest@types/lodash.debounce@types/lodash.memoize@types/lodash.reduce@types/lodash.throttle@types/react@types/react-dombabel-runtimeclassnameslessless-plugin-npm-importnav-frontend-skjemanpm-run-allpostcss-assetsprettierprop-typesreact-momentrolluprollup-plugin-babelrollup-plugin-commonjsrollup-plugin-imgrollup-plugin-jsonrollup-plugin-node-resolverollup-plugin-peer-deps-externalrollup-plugin-postcssrollup-plugin-sourcemapsrollup-plugin-typescript2rollup-plugin-urltypescript
react-component-lib
This is a boilerplate repository for creating npm packages with React components written in TypeScript and using styled-components.
Medium article explaining step by step how to use this repo to publish your own library to NPM: https://medium.com/@xfor/developing-publishing-react-component-library-to-npm-styled-components-typescript-cc8274305f5a
Installation:
To install all dependencies run npm run install-all.
Developing your library:
To start developing your library, run npm run dev. It will build your library and run example create-react-app where you can test your components. Each time you make changes to your library or example app, app will be reloaded to reflect your changes.
Styled-components:
Developing library with components built with styled-components is challenging because you have to keep only one instance of styled-components. If you would just symlink your library (file:../ or npm link) to example app that is also using styled-components you'll get a console warning about multiple instances of styled-components (even though styled-components are peer dependency) and your styles will be possibly broken. To be able to conveniently develop styled components I am injecting bundled files directly into example app's /src folder and importing it in App.tsx along with type declaration.
Typescript
This boilerplate lets you develop your libraries in Typescript and you can simultaneously test it in Typescript example create-react-app.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE.md:0
- Info: FSF or OSI recognized license: MIT License: LICENSE.md:0
Reason
SAST tool is run on all commits
Details
- Info: all commits (14) are checked with a SAST tool
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/navikt/.github/SECURITY.md:1
- Info: Found linked content: github.com/navikt/.github/SECURITY.md:1
- Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy
- Info: Found text in security policy: github.com/navikt/.github/SECURITY.md:1
Reason
6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-test.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/build-and-test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-and-test.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/build-and-test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-beta.yaml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/publish-beta.yaml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-beta.yaml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/publish-beta.yaml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish-beta.yaml:58: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/publish-beta.yaml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish-release.yaml:73: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/publish-release.yaml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-release.yaml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/publish-release.yaml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-release.yaml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/publish-release.yaml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish-release.yaml:57: update your workflow using https://app.stepsecurity.io/secureworkflow/navikt/arbeidsforhold/publish-release.yaml/main?enable=pin
- Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 third-party GitHubAction dependencies pinned
- Info: 3 out of 3 npmCommand dependencies pinned
Reason
Found 0/21 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/publish-beta.yaml:25
- Warn: jobLevel 'packages' permission set to 'write': .github/workflows/publish-beta.yaml:26
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/publish-release.yaml:11
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/publish-release.yaml:23
- Warn: jobLevel 'packages' permission set to 'write': .github/workflows/publish-release.yaml:24
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/publish-release.yaml:67
- Warn: no topLevel permission defined: .github/workflows/build-and-test.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish-beta.yaml:1
- Warn: no topLevel permission defined: .github/workflows/publish-release.yaml:1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
11 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-vg6x-rcgg-rjx6
- Warn: Project is vulnerable to: GHSA-x574-m823-4x7w
- Warn: Project is vulnerable to: GHSA-4r4m-qw57-chr8
- Warn: Project is vulnerable to: GHSA-xcj6-pq6g-qj4x
- Warn: Project is vulnerable to: GHSA-356w-63v5-8wf4
- Warn: Project is vulnerable to: GHSA-859w-5945-r5v3
- Warn: Project is vulnerable to: GHSA-9crc-q9x8-hgqq
Score
4.9
/10
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