Gathering detailed insights and metrics for import-map-overrides
Gathering detailed insights and metrics for import-map-overrides
Installations
npm install import-map-overridesDeveloper
joeldenning
Developer Guide
BETA
Module System
ESM
Min. Node Version
Typescript Support
No
Node Version
22.9.0
NPM Version
10.8.3
Statistics
341 Stars
177 Commits
47 Forks
8 Watching
15 Branches
15 Contributors
Updated on 29 Oct 2024
Languages
JavaScript (90.31%)
HTML (6.08%)
CSS (3.62%)
Total Downloads
Cumulative downloads
Total Downloads
2,094,251
Last day
10.3%
2,806
Compared to previous day
Last week
13.4%
15,768
Compared to previous week
Last month
7.7%
62,397
Compared to previous month
Last year
49.3%
783,606
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Dev Dependencies
34
@babel/core@babel/eslint-parser@babel/plugin-proposal-class-properties@babel/plugin-transform-react-jsx@babel/preset-env@changesets/changelog-github@changesets/cli@eslint/eslintrc@eslint/js@rollup/plugin-babel@rollup/plugin-node-resolve@testing-library/jest-dombabel-jestconcurrentlycopyfilescross-enveslinteslint-config-important-stuffeslint-plugin-es5huskyjestjest-clijest-environment-jsdomjest-fetch-mockpostcsspreactprettierpretty-quickregenerator-runtimerimrafrolluprollup-plugin-postcssrollup-plugin-terserserve
Versions
import-map-overrides
A browser and nodejs javascript library for being able to override import maps. This works with native browser import maps, SystemJS import maps, es-module-shims import maps, and more.
Motivation
Import maps are a way of controlling which url to download javascript modules from. The import-map-overrides library allows you to dynamically change the url for javascript modules by storing overrides in local storage. This allows developers to override individual modules to point to their localhost during development of a module, without having to boot up a local environment with all the other modules and a backend server.
You should not use import-map-overrides as the only import map on your page, since you cannot count on everyone's local storage having valid values for all of your modules. Instead, import-map-overrides should be viewed as a developer experience enhancement and dev tool -- developers can develop and debug on deployed environments instead of having to boot up a local environment.
Here are some tutorial videos that explain this in more depth:
Documentation
The UI for import-map-overrides works in evergreen browsers (web components support required). The javascript API works in IE11+.
Browser
NodeJS
Contributing
Make sure you commit a changeset with pnpm changeset before you open a PR.
This will allow to automatically bump the version and maintain the CHANGELOG
once released.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
- Info: security policy file detected: docs/security.md:1
- Info: Found linked content: docs/security.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: docs/security.md:1
- Info: Found text in security policy: docs/security.md:1
Reason
no binaries found in the repo
Reason
12 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
4 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-7q7g-4xm8-89cq
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
Reason
Found 8/25 approved changesets -- score normalized to 3
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test-release.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/single-spa/import-map-overrides/build-test-release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test-release.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/single-spa/import-map-overrides/build-test-release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test-release.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/single-spa/import-map-overrides/build-test-release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test-release.yml:55: update your workflow using https://app.stepsecurity.io/secureworkflow/single-spa/import-map-overrides/build-test-release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test-release.yml:58: update your workflow using https://app.stepsecurity.io/secureworkflow/single-spa/import-map-overrides/build-test-release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-test-release.yml:61: update your workflow using https://app.stepsecurity.io/secureworkflow/single-spa/import-map-overrides/build-test-release.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-test-release.yml:74: update your workflow using https://app.stepsecurity.io/secureworkflow/single-spa/import-map-overrides/build-test-release.yml/main?enable=pin
- Info: 0 out of 4 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 third-party GitHubAction dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: jobLevel 'contents' permission set to 'write': .github/workflows/build-test-release.yml:49
- Warn: no topLevel permission defined: .github/workflows/build-test-release.yml:1
Reason
no effort to earn an OpenSSF best practices badge detected
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 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 20 are checked with a SAST tool
Score
4.9
/10
Last Scanned on 2024-11-18
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