npmpackage.info

Gathering detailed insights and metrics for @cerner/duplicate-package-checker-webpack-plugin

@cerner/duplicate-package-checker-webpack-plugin

Terra Toolkit is a monorepo that contains utility modules for use when developing using Terra components

2.6.0

Apache-2.0

JavaScript

19.82 kB

3,870,586 3.7

Installations

npm install @cerner/duplicate-package-checker-webpack-plugin

Pull Requests

Open

0

Total

619

Closed

52

Merged

567

Issues

Open

1

Total

222

Closed

221

Releases

v2.11.0

Published on 11 Apr 2018

2.5.0

v2.5.0

Published on 03 Jan 2018

v2.0.0

Published on 31 Aug 2017

v1.2.2

Published on 14 Jul 2017

v1.2.1

Published on 13 Jul 2017

v1.2.0

Published on 13 Jul 2017

View all 7 releases

Developer

cerner

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

10 || 12 || 14

Typescript Support

No

Node Version

14.21.3

NPM Version

lerna/6.6.2/node@v14.21.3+x64 (linux)

Statistics

32 Stars

859 Commits

37 Forks

30 Watching

76 Branches

67 Contributors

Updated on 22 May 2024

Bundle Size

58.32 kB

Minified

19.82 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (91.84%)

MDX (8.09%)

SCSS (0.05%)

Dockerfile (0.01%)

CSS (0.01%)

Total Downloads

Cumulative downloads

Total Downloads

3,870,586

Last day

23.3%

3,683

Compared to previous day

Last week

-6.9%

19,712

Compared to previous week

Last month

2.3%

97,347

Compared to previous month

Last year

24.8%

1,599,763

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Versions

Terra Toolkit

Terra Toolkit is a Lerna repository for common development packages necessary for developing Terra projects.

Notice
Package Status
Versioning
Contributing
Local Development
Local Development using Docker (Dev Containers)
LICENSE

Notice

The code for the terra-toolkit npm dependency has been moved to terra-toolkit-boneyard.

Package Status

Package	Version	Status	Dependencies
@cerner/browserslist-config-terra
@cerner/eslint-config-terra
@cerner/terra-functional-testing

Versioning

Terra-toolkit packages are considered to be stable and will follow SemVer for versioning.

MAJOR versions represent breaking changes
MINOR versions represent added functionality in a backwards-compatible manner
PATCH versions represent backwards-compatible bug fixes

Consult the component CHANGELOGs, related issues, and PRs for more information.

Contributing

Please read through our contributing guidelines. Included are directions for issue reporting and pull requests.

Local Development

Install docker https://www.docker.com/ to run browser tests.
Install dependencies and run tests.

1npm install
2npm run test

Local Development using Docker (Dev Containers)

Install Rancher or Docker.
- Rancher is free and open-source and is highly recommended whereas Docker may require a license for use.
Install Microsoft VS Code.
Install the Dev Container extension.
- Navigate to View -> Extension -> Search for and install Dev Containers (or "ms-vscode-remote.remote-containers")
- More information on Dev Containers
Build the dev container:
- (Option 1) - Opening local workspace in dev container
  - Clone the repository (or fork) locally and open the project in Visual Studio Code
  - Navigate to View -> Command Palette and run Dev Containers: Open Workspace in Container
- (Option 2) - Recommended for Windows for hot-reloading to work during development and improved performance: Creating the dev container using dev volumes (for more information and guidance, see the Official Guide)
  - If you have git setup and have global config file ~/.gitconfig locally, these settings should automatically be transferred to the dev container
  - Navigate to View -> Command Palette and run Dev Containers: Clone Repository in Container Volume
  - Paste the GitHub URL of this repository (or fork)
  - VS Code will now reload the workspace and create/start the dev container and volume
  - Please note: changes made using this option will only update files in the Docker volume. It is recommended to commit changes often in case the volume is deleted or dev container gets removed.
You're now running in a dev container. Use the terminal of the dev container in Visual Studio Code to issue any npm or bash commands.
Before running any WDIO tests, make sure to perform the following steps:
- Open a new terminal (outside the dev container) and navigate to ".devcontainer/" path in your repository.
- Execute the command "docker compose -f docker-compose-wdio.yml up". Selenium hub should spin up. Leave this running in the background. If you see errors saying "container name already exists", run "docker container prune" command followed by pressing "y" to clear up any unused containers and try running the previous command again.
- You can now run npm run test:docker or npm run wdio:docker commands to run WDIO tests from inside the Dev Container.
- NOTE: Optionally, if you want to run other WDIO commands in the dev container, you can also edit the root package.json file WDIO scripts to include --disableSeleniumService=true flag. This will disable the selenium service from spinning up again. For example:
```
1"scripts": {
2 "wdio-fusion": "terra wdio --disable-selenium-service=true --themes orion-fusion-theme",
3 }
```
To terminate a dev container:
- Use command line or Rancher/Docker Desktop OR
- Using Visual Studio Code
  - Select the Remote Explorer icon in the Activity Bar or View -> Command Palette and run Remote Explorer: Focus on Containers View
  - Locate the terra-toolkit_devcontainer or currently running dev container under "Dev Containers"
  - Right click and select Stop Container and close the workspace
    - You can also select Rebuild Container to restart the dev container
To reopen a dev container:
- Existing local workspace (for Option 1)
  - Open the project in Visual Studio Code
  - Ensure the workspace contains the .devcontainer folder
  - Navigate to View -> Command Palette and run Dev Containers: Open Workspace in Container
- Isolated dev container volume (for Option 2)
  - Open Visual Studio Code
  - Use the Remote Explorer icon in the Activity Bar or View -> Command Palette and run Remote Explorer: Focus on Containers View to view containers
  - Locate the terra-toolkit_devcontainer under "Dev Containers"
  - Hover over the dev container and click the Folder icon labelled Open Folder in Container or by right clicking and selecting Open Folder in Container

LICENSE

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

9

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci-cd.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/ci-cd.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci-cd.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/ci-cd.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci-cd.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/ci-cd.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci-cd.yml:50: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/ci-cd.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci-cd.yml:64: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/ci-cd.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci-cd.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/ci-cd.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-close.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-close.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-close.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-close.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-close.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-close.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:51: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:67: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:95: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:103: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-preview.yml:117: update your workflow using https://app.stepsecurity.io/secureworkflow/cerner/terra-toolkit/pr-preview.yml/main?enable=pin
Warn: containerImage not pinned by hash: .devcontainer/Dockerfile:1
Warn: containerImage not pinned by hash: Dockerfile:2
Info: 0 out of 5 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 13 third-party GitHubAction dependencies pinned
Info: 0 out of 2 containerImage dependencies pinned

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3.7

/10

Last Scanned on 2024-11-25

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

@cerner/duplicate-package-checker-webpack-plugin

Installations

Pull Requests

0

619

52

567

Issues

1

222

221

Releases

Developer

Developer Guide

CommonJS

10 || 12 || 14

No

14.21.3

lerna/6.6.2/node@v14.21.3+x64 (linux)

Statistics

Bundle Size

58.32 kB

19.82 kB

Languages

Total Downloads

3,870,586

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Peer Dependencies

Dev Dependencies

Terra Toolkit

Notice

Package Status

Versioning

Contributing

Local Development

Local Development using Docker (Dev Containers)

LICENSE

10

10

10

9

0

0

0

0

0

0

0

0

3.7

/10