Gathering detailed insights and metrics for rollup-plugin-typescript-paths-vtn
Gathering detailed insights and metrics for rollup-plugin-typescript-paths-vtn
Rollup Plugin to automatically resolve path aliases set in the compilerOptions section of tsconfig.json.
Installations
npm install rollup-plugin-typescript-paths-vtnDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Score
68.1
Supply Chain
85.9
Quality
75.2
Maintenance
100
Vulnerability
99.6
License
Releases
11
Languages
2
TypeScript
JavaScript
TypeScript (54.29%)
JavaScript (45.71%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
46 Stars
53 Commits
13 Forks
2 Watchers
1 Branches
5 Contributors
Updated on Jan 16, 2025
Maintainers
1
Package Meta Information
Latest Version
1.2.3
Package Id
rollup-plugin-typescript-paths-vtn@1.2.3
Unpacked Size
14.42 kB
Size
5.88 kB
File Count
31
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
1
Dev Dependencies
3
rollup-plugin-typescript-paths
Rollup Plugin to automatically resolve path aliases set in the compilerOptions section of tsconfig.json. It assumes that your Typescript code has already been transpiled before being rolled up (if that's not the case, you should probably use rollup-plugin-typescript).
For example, if you have
1// tsconfig.json 2{ 3 "compilerOptions": { 4 // ... 5 "baseUrl": ".", 6 "paths": { 7 "@utils": ["src/helpers/utils"] 8 } 9 } 10}
1import { something } from '@utils';
Then this plugin will make sure that rollup knows how to resolve @utils.
Features
- No config required. 😎
- Wildcards are supported. 💪
- Uses
nodeModuleNameResolverfrom the Typescript API. 🤓
Installation
npm install --save-dev rollup-plugin-typescript-paths
Usage
1import { typescriptPaths } from 'rollup-plugin-typescript-paths'; 2 3export default { 4 // ... 5 plugins: [ 6 typescriptPaths() 7 ] 8}
Options
tsConfigPath: Custom path to yourtsconfig.json. Use this if the plugin can't seem to find the correct one by itself.absolute: Whether to resolve to absolute paths or not; defaults totrue.transform: If the plugin successfully resolves a path, this function allows you to hook into the process and transform that path before it is returned.
License
MIT.
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:0
- Info: FSF or OSI recognized license: MIT License: license:0
Reason
0 existing vulnerabilities detected
Reason
Found 3/30 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/simonhaenisch/rollup-plugin-typescript-paths/main.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/simonhaenisch/rollup-plugin-typescript-paths/main.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/main.yml:26
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/main.yml:1
- Info: no jobLevel write permissions found
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 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 4 are checked with a SAST tool
Score
3.5
/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