Skip to content

Update dependency ng-packagr to v10 [SECURITY] - #13

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-ng-packagr-vulnerability
Open

Update dependency ng-packagr to v10 [SECURITY]#13
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-ng-packagr-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Apr 8, 2024

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ng-packagr ^9.0.0^10.0.0 age adoption passing confidence

OS Command Injection in ng-packagr

CVE-2020-7735 / GHSA-qm28-7hqv-wg5j

More information

Details

The package ng-packagr before 10.1.1 are vulnerable to Command Injection via the styleIncludePaths option.

Severity

  • CVSS Score: 6.6 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

ng-packagr/ng-packagr (ng-packagr)

v10.1.1

Compare Source

v10.1.0

Compare Source

v10.0.4

Compare Source

v10.0.3

Compare Source

v10.0.2

Compare Source

v10.0.1

Compare Source

v10.0.0

Compare Source

Features
  • improve progress reporting (3a9827f)
Bug Fixes

Configuration

📅 Schedule: (in timezone Europe/Zurich)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 931c32e to 6b04bfd Compare August 14, 2025 20:05
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 6b04bfd to 3ae81b5 Compare September 26, 2025 07:52
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 3ae81b5 to 532ddff Compare October 25, 2025 19:58
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch 2 times, most recently from fe972cc to 94cde7f Compare November 19, 2025 07:09
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 94cde7f to fecec9d Compare January 19, 2026 23:02
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from fecec9d to f95dac9 Compare March 8, 2026 12:00
@renovate renovate Bot changed the title chore(deps): update dependency ng-packagr to v10 [security] Update dependency ng-packagr to v10 [SECURITY] Apr 15, 2026
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from f95dac9 to 44d43fa Compare April 15, 2026 11:50
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 44d43fa to 7401531 Compare May 1, 2026 11:59
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 7401531 to c74011b Compare May 23, 2026 08:15
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from c74011b to ea163d2 Compare June 13, 2026 07:42
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from ea163d2 to 1e253b1 Compare July 18, 2026 03:48
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 1e253b1 to 23a3fe5 Compare July 31, 2026 00:11
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 23a3fe5 to 18f5c4d Compare August 15, 2026 15:57
@renovate
renovate Bot force-pushed the renovate/npm-ng-packagr-vulnerability branch from 18f5c4d to d90aec2 Compare August 30, 2026 07:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants