Installations
npm install @xpack-dev-tools/windows-build-toolsDeveloper Guide
Typescript
No
Module System
N/A
Node Version
18.18.2
NPM Version
10.8.2
Score
49.5
Supply Chain
44
Quality
76.7
Maintenance
100
Vulnerability
100
License
Releases
xPack Windows Build Tools v4.4.1-3
Updated on Sep 13, 2024
xPack Windows Build Tools v4.4.1-2
Updated on Nov 14, 2023
xPack Windows Build Tools v4.4.1-1
Updated on Sep 05, 2023
xPack Windows Build Tools v4.4.0-1
Updated on Jan 29, 2023
xPack Windows Build Tools v4.3.0-1
Updated on Mar 05, 2022
xPack Windows Build Tools v4.2.1-3
Updated on Oct 18, 2021
Contributors
Unable to fetch Contributors
Languages
MDX (72.07%)
TypeScript (12.01%)
Shell (9.99%)
CSS (2.62%)
JavaScript (1.92%)
C (1.38%)
Makefile (0.01%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
Download Statistics
Total Downloads
25,005
Last Day
69
Last Week
351
Last Month
1,354
Last Year
7,421
GitHub Statistics
MIT License
195 Stars
434 Commits
59 Forks
23 Watchers
5 Branches
2 Contributors
Updated on Feb 10, 2025
Maintainers
Package Meta Information
Latest Version
4.4.1-3.1
Package Id
@xpack-dev-tools/windows-build-tools@4.4.1-3.1
Unpacked Size
13.60 kB
Size
5.12 kB
File Count
4
NPM Version
10.8.2
Node Version
18.18.2
Published on
Sep 13, 2024
Total Downloads
Cumulative downloads
Total Downloads
25,005
Last Day
97.1%
69
Compared to previous day
Last Week
66.4%
351
Compared to previous week
Last Month
116.3%
1,354
Compared to previous month
Last Year
45.1%
7,421
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
No dependencies detected.
The xPack Windows Build Tools
A standalone Windows specific package (not a full multi-platform xPack),
customised for the requirements of the Eclipse Embedded CDT managed build
projects; it includes a recent version of GNU make and a recent version of
BusyBox, which provides a convenient implementation for sh/rm/echo.
In addition to the package meta data, this project also includes the build scripts.
Overview
This open source project is hosted on GitHub as
xpack-dev-tools/windows-build-tools-xpack
and provides the platform specific binaries for the
xPack Windows Build Tools.
The binaries can be installed automatically as binary xPacks or manually as portable archives.
Release schedule
This distribution generally follows the official make, but there is no commitment of a quick release cycle.
User info
This section is intended as a shortcut for those who plan to use the xPack Windows Build Tools binaries. For full details please read the xPack Windows Build Tools pages.
Easy install
The easiest way to install Windows Build Tools is using the binary xPack, available as
@xpack-dev-tools/windows-build-tools
from the npmjs.com registry.
Prerequisites
A recent xpm, which is a portable Node.js command line application that complements npm with several extra features specific to C/C++ projects.
It is recommended to install/update to the latest version with:
1npm install --location=global xpm@latest
For details please follow the instructions in the xPack install page.
Install
With the xpm tool available, installing
the latest version of the package and adding it as
a development dependency for a project is quite easy:
1cd my-project 2xpm init # Add a package.json if not already present 3 4xpm install @xpack-dev-tools/windows-build-tools@latest --verbose 5 6ls -l xpacks/.bin
This command will:
- install the latest available version, into the central xPacks store, if not already there
- add symbolic links to the central store
(or
.cmdforwarders on Windows) into the localxpacks/.binfolder.
The central xPacks store is a platform dependent
location in the home folder;
check the output of the xpm command for the actual
folder used on your platform.
This location is configurable via the environment variable
XPACKS_STORE_FOLDER; for more details please check the
xpm folders page.
For xPacks aware tools, like the Eclipse Embedded C/C++ plug-ins, it is also possible to install Windows Build Tools globally, in the user home folder:
1xpm install --global @xpack-dev-tools/windows-build-tools@latest --verbose
Eclipse will automatically
identify binaries installed with
xpm and provide a convenient method to manage paths.
After install, the package should create a structure like this (macOS files; only the first two depth levels are shown):
1$ tree -L 2 /Users/ilg/.local/xPacks/@xpack-dev-tools/windows-build-tools/4.4.1-2/.content/ 2/Users/ilg/.local/xPacks/@xpack-dev-tools/windows-build-tools/4.4.1-2/.content/ 3├── bin 4│ ├── busybox.exe 5│ ├── cp.exe 6│ ├── echo.exe 7│ ├── make.exe 8│ ├── mkdir.exe 9│ ├── rm.exe 10│ └── sh.exe 11├── distro-info 12│ └── licenses 13├── include 14│ └── gnumake.h 15├── README.md 16└── share 17 ├── info 18 └── man 19 207 directories, 9 files
No other files are installed in any system folders or other locations.
Uninstall
To remove the links created by xpm in the current project:
1cd my-project 2 3xpm uninstall @xpack-dev-tools/windows-build-tools
To completely remove the package from the central xPack store:
1xpm uninstall --global @xpack-dev-tools/windows-build-tools
Manual install
For all platforms, the xPack Windows Build Tools binaries are released as portable archives that can be installed in any location.
The archives can be downloaded from the GitHub Releases page.
For more details please read the Install page.
Versioning
The version strings used by the GNU make project are three number strings
like 4.4.1; to this string the xPack distribution adds a four number,
but since semver allows only three numbers, all additional ones can
be added only as pre-release strings, separated by a dash,
like 4.4.1-2. When published as a npm package, the version gets
a fifth number, like 4.4.1-2.1.
Since adherence of third party packages to semver is not guaranteed,
it is recommended to use semver expressions like ^4.4.1 and ~4.4.1
with caution, and prefer exact matches, like 4.4.1-2.1.
Maintainer info
For maintainer info, please see the README-MAINTAINER.
Support
The quick advice for getting support is to use the GitHub Discussions.
For more details please read the Support page.
License
Unless otherwise stated, the content is released under the terms of the MIT License, with all rights reserved to Liviu Ionescu.
The binary distributions include several open-source components; the
corresponding licenses are available in the installed
distro-info/licenses folder.
Download analytics
- GitHub gnu-mcu-eclipse/windows-build-tools.git
- latest release
- all releases
- latest release
- xPack @gnu-mcu-eclipse/windows-build-tools
- latest release, per month
- all releases
- latest release, per month
- individual file counters (grouped per release)
Credits to Shields IO and Somsubhra/github-release-stats.
No vulnerabilities found.
Reason
26 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
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
4 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
- Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
Reason
dependency not pinned by hash detected -- score normalized to 1
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-win32-x64.yml:102: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/build-win32-x64.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-win32-x64.yml:144: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/build-win32-x64.yml/xpack?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/build-win32-x64.yml:152: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/build-win32-x64.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-win32-x64.yml:195: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/build-win32-x64.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/build-win32-x64.yml:200: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/build-win32-x64.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-github-pages.yml:62: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-github-pages.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-github-pages.yml:69: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-github-pages.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-github-pages.yml:81: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-github-pages.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-github-pages.yml:85: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-github-pages.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-github-pages.yml:93: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-github-pages.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-release.yml:64: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-release.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-release.yml:69: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-release.yml/xpack?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish-release.yml:85: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-release.yml/xpack?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish-release.yml:108: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/publish-release.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-prime.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/test-prime.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-prime.yml:80: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/test-prime.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-prime.yml:113: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/test-prime.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-prime.yml:118: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/test-prime.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-xpm.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/test-xpm.yml/xpack?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test-xpm.yml:80: update your workflow using https://app.stepsecurity.io/secureworkflow/xpack-dev-tools/windows-build-tools-xpack/test-xpm.yml/xpack?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/build-win32-x64.yml:109
- Warn: npmCommand not pinned by hash: .github/workflows/publish-release.yml:79
- Info: 0 out of 17 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 3 third-party GitHubAction dependencies pinned
- Info: 1 out of 3 npmCommand dependencies pinned
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/build-win32-x64.yml:1
- Warn: no topLevel permission defined: .github/workflows/deep-clean.yml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/publish-github-pages.yml:41
- Warn: no topLevel permission defined: .github/workflows/publish-release.yml:1
- Warn: no topLevel permission defined: .github/workflows/test-prime.yml:1
- Warn: no topLevel permission defined: .github/workflows/test-xpm.yml:1
- Info: no jobLevel write permissions found
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
Project has not signed or included provenance with any releases.
Details
- Warn: release artifact v4.4.1-3 not signed: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/174910503
- Warn: release artifact v4.4.1-2 not signed: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/129307496
- Warn: release artifact v4.4.1-1 not signed: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/119924472
- Warn: release artifact v4.4.0-1 not signed: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/90598965
- Warn: release artifact v4.3.0-1 not signed: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/61053431
- Warn: release artifact v4.4.1-3 does not have provenance: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/174910503
- Warn: release artifact v4.4.1-2 does not have provenance: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/129307496
- Warn: release artifact v4.4.1-1 does not have provenance: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/119924472
- Warn: release artifact v4.4.0-1 does not have provenance: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/90598965
- Warn: release artifact v4.3.0-1 does not have provenance: https://api.github.com/repos/xpack-dev-tools/windows-build-tools-xpack/releases/61053431
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
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'xpack'
- Warn: branch protection not enabled for branch 'xpack-development'
- Warn: branch protection not enabled for branch 'xpack-develop'
- Warn: branch protection not enabled for branch 'master'
Score
3.7
/10
Last Scanned on 2025-02-03
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