@oslokommune/punkt-vue
Vue komponentbibliotek til Punkt, et designsystem laget av Oslo Origo
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/progressbar-D0bYOpFA.cjs | AI (source-diff): Standard Vite/Rollup minified component output; not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:dist/footersimple-XWF7n0Rn.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library. | ai | |
| source-diff | obfuscated-file:dist/header-C4IVQjWR.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library. | ai | |
| source-diff | obfuscated-file:dist/InputWrapper-B3nYy5_K.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library. | ai | |
| source-diff | obfuscated-file:dist/progressbar-CEeMS3Co.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library. | ai | |
| source-diff | obfuscated-file:dist/footer-CXFzikEP.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library; content is readable component code. | ai | |
| source-diff | obfuscated-file:dist/textarea-XFN-R8Q8.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library. | ai | |
| source-diff | obfuscated-file:dist/textinput-DeSHl-64.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Component library with per-component chunk splitting; large file counts are expected on version bumps. | ai | |
| source-diff | obfuscated-file:dist/table-Vea6ecvM.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output for Vue component library. | ai |
Versions (showing 51 of 97)
| Version | Deps | Published |
|---|---|---|
| 16.24.1 | 0 / 12 | |
| 16.23.0 | 0 / 12 | |
| 16.22.0 | 0 / 12 | |
| 16.21.1 | 0 / 12 | |
| 16.21.0 | 0 / 12 | |
| 16.19.0 | 0 / 12 | |
| 16.18.0 | 0 / 12 | |
| 16.17.3 | 0 / 12 | |
| 16.17.2 | 0 / 12 | |
| 16.17.1 | 0 / 12 | |
| 16.17.0 | 0 / 12 | |
| 16.16.1 | 0 / 12 | |
| 16.16.0 | 0 / 12 | |
| 16.15.3 | 0 / 12 | |
| 16.15.1 | 0 / 12 | |
| 16.15.0 | 0 / 12 | |
| 16.14.0 | 0 / 12 | |
| 16.13.3 | 0 / 12 | |
| 16.13.2 | 0 / 12 | |
| 16.13.1 | 0 / 12 | |
| 16.13.0 | 0 / 12 | |
| 16.12.0 | 0 / 12 | |
| 16.11.1 | 0 / 12 | |
| 16.11.0 | 0 / 12 | |
| 16.10.0 | 0 / 12 | |
| 16.9.1 | 0 / 12 | |
| 16.9.0 | 0 / 12 | |
| 16.8.2 | 0 / 12 | |
| 16.7.7 | 0 / 12 | |
| 16.7.6 | 0 / 12 | |
| 16.7.5 | 0 / 12 | |
| 16.7.4 | 0 / 9 | |
| 16.7.3 | 0 / 9 | |
| 16.7.2 | 0 / 9 | |
| 16.7.1 | 0 / 9 | |
| 16.7.0 | 0 / 9 | |
| 16.6.2 | 0 / 9 | |
| 16.6.1 | 0 / 9 | |
| 16.6.0 | 0 / 9 | |
| 16.5.1 | 0 / 9 | |
| 16.5.0 | 0 / 9 | |
| 16.4.0 | 0 / 9 | |
| 16.3.0 | 0 / 9 | |
| 16.2.0 | 0 / 9 | |
| 16.1.0 | 0 / 9 | |
| 16.0.5 | 0 / 9 | |
| 16.0.4 | 0 / 9 | |
| 16.0.3 | 0 / 9 | |
| 16.0.2 | 0 / 9 | |
| 16.0.0 | 0 / 9 | |
| 15.4.5 | 0 / 9 |
v16.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.11.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.11.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.10.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.9.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.9.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.8.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.4
9 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.