Gathering detailed insights and metrics for @navikt/arbeidsforhold
Gathering detailed insights and metrics for @navikt/arbeidsforhold
Installations
npm install @navikt/arbeidsforholdDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Min. Node Version
>=8
Node Version
14.16.0
NPM Version
6.14.11
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
50
Package Meta Information
Latest Version
1.4.2
Package Id
@navikt/arbeidsforhold@1.4.2
Unpacked Size
3.40 MB
Size
1.25 MB
File Count
51
NPM Version
6.14.11
Node Version
14.16.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
Dependencies
1
Peer Dependencies
35
@navikt/fnrvalidator@react-pdf/rendererclassnameslodash.throttlemomentnav-frontend-alertstripernav-frontend-alertstriper-stylenav-frontend-chevronnav-frontend-chevron-stylenav-frontend-corenav-frontend-hjelpetekstnav-frontend-hjelpetekst-stylenav-frontend-ikoner-assetsnav-frontend-js-utilsnav-frontend-lenkernav-frontend-lenker-stylenav-frontend-lukknappnav-frontend-lukknapp-stylenav-frontend-modalnav-frontend-modal-stylenav-frontend-paneler-stylenav-frontend-popovernav-frontend-popover-stylenav-frontend-skjemanav-frontend-skjema-stylenav-frontend-spinnernav-frontend-spinner-stylenav-frontend-tabsnav-frontend-tabs-stylenav-frontend-typografinav-frontend-typografi-stylereactreact-modalreact-momentreact-scripts
Dev Dependencies
63
@babel/core@babel/plugin-proposal-class-properties@babel/preset-typescript@navikt/fnrvalidator@react-pdf/renderer@rollup/plugin-image@svgr/rollup@types/fetch-mock@types/jest@types/react@types/react-dom@types/react-router-dombabel-polyfillbabel-runtimeclassnamesgh-pageslessless-plugin-npm-importlodash.throttlemomentnav-frontend-alertstripernav-frontend-alertstriper-stylenav-frontend-chevronnav-frontend-chevron-stylenav-frontend-corenav-frontend-hjelpetekstnav-frontend-hjelpetekst-stylenav-frontend-ikoner-assetsnav-frontend-js-utilsnav-frontend-lenkernav-frontend-lenker-stylenav-frontend-lukknappnav-frontend-lukknapp-stylenav-frontend-modalnav-frontend-modal-stylenav-frontend-paneler-stylenav-frontend-popovernav-frontend-popover-stylenav-frontend-skjemanav-frontend-skjema-stylenav-frontend-spinnernav-frontend-spinner-stylenav-frontend-tabsnav-frontend-tabs-stylenav-frontend-typografinav-frontend-typografi-stylenpm-run-allprettierprop-typesreactreact-modalreact-momentrolluprollup-plugin-babelrollup-plugin-commonjsrollup-plugin-jsonrollup-plugin-node-resolverollup-plugin-peer-deps-externalrollup-plugin-postcssrollup-plugin-sourcemapsrollup-plugin-typescript2rollup-plugin-urltypescript
NAV Arbeidsforhold
|
|
React moduler / mikro-frontends som viser brukerens arbeidsforhold
Installasjon
npm install @navikt/arbeidsforhold
Komponenter
Prosjektet er delt opp i uavhengige moduler som kan importeres
Liste med arbeidsforhold
1import { ListeMedArbeidsforhold } from "@navikt/arbeidsforhold";
Eksempel
1 onClick = { 2 type: "KNAPP", 3 getId: (arbeidsforholdId: string) => console.log(arbeidsforholdId) 4 }; 5 6 return <ListeMedArbeidsforhold 7 locale={"nb" as "nb" | "en"} 8 miljo={"DEV" as "LOCAL" | "DEV" | "PROD"} 9 onClick={this.onClick} />;
Onclick støtter følgende variasjoner
1 | { 2 type: "INGEN_ON_CLICK"; 3 } 4 | { 5 type: "LENKE"; 6 href: string; 7 } 8 | { 9 type: "REACT_ROUTER_LENKE"; 10 Component: typeof Link; 11 to: string; 12 } 13 | { 14 type: "KNAPP"; 15 getId: (navArbeidsforholdId: number) => void; 16 };
Ved implementasjon av REACT_ROUTER_LENKE må {Link} importeres fra react-router-dom i rot-applikasjonen.
Se komplett eksempel under mappen /example
Detaljert arbeidsforhold
1import { DetaljertArbeidsforhold } from "@navikt/arbeidsforhold";
Eksempel
1render = () => { 2 const id = "82421242"; 3 const locale = "nb" as "nb" | "en"; 4 const miljo = "DEV" as "LOCAL" | "DEV" | "PROD"; 5 const rolle = "ARBEIDSTAKER" as "ARBEIDSTAKER" | "ARBEIDSGIVER" 6 7 return <DetaljertArbeidsforhold 8 navArbeidsforholdId={id} 9 locale={locale} 10 miljo={miljo} 11 rolle={rolle} />; 12};
Komponenten vil hente data fra arbeidsforhold-api basert på miljo-variabelen, med mindre customApiUrl er satt. CustomApiUrl må inneholde {id} som erstattes av navArbeidsforholdId. Eksempel: "https://din-api-proxy.nav.no/arbeidsforhold/{id}"
Videreutvikling / test
- Hent repoet fra github
git clone https://github.com/navikt/arbeidsforhold.git
- Installer nødvendige pakker, start mock-container og start applikasjonen
npm install && docker-compose up -d && npm start
Test-applikasjonen består av en simpel create-react-app som importerer og benytter pakkene
Prosjektet støtter hot-reloading, endringer i komponentene vil føre til at test-applikasjonen oppdateres
Deployering
Dev
- Besøk https://github.com/navikt/personopplysninger/actions
- Velg workflow
Deploy-to-webog deretterRun workflow. Husk å velge hvilken branch du ønsker å deploye til dev.
eller
Benytt Github CLI for å deploye via kommandolinjen:
gh workflow run workflow_dispatch -b <navn_på_branch>
Push deretter den nye versjonen til Github, som vil plukkes opp av Github Actions.
Prod
Deploy til prod trigges når du tagger og pusher en ny versjon. Husk å skrive en kort beskrivelse slik at det er enkelt å sporte endringer historisk fra én versjon til en annen.
- Opprett PR og be om review fra en kollega.
- Merge godkjent PR inn i master.
npm version [minor | patch] -m "%s: Noen få ord om endringene som er gjort."- Gå til repoet og publiser en ny release eller bruk kommandolinjen:
gh release create vx.x.x -t "Tittel på release"
Om semver
npm version patch vil bumpe versjon fra feks v1.1.1 til v1.1.2. Diskuter med teamet om versjonen er en minor eller kun en patch. Hvis minor bruker du npm version minor istedet. Du kan lese mer på semver.org
Logging
Vi bruker fo-frontendlogger for logging. For oppslag i kibana:
application:frontendlogger AND x_appname:arbeidsforhold
Henvendelser
Spørsmål knyttet til koden eller prosjektet kan rettes mot https://github.com/orgs/navikt/teams/team-personbruker
For NAV-ansatte
Interne henvendelser kan sendes via Slack i kanalen #team-personbruker.
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