Skip to content

build: enable minimumReleaseAge to mitigate dependency chain attacks#13

Merged
devversion merged 1 commit intoangular:mainfrom
alan-agius4:min-age
Sep 17, 2025
Merged

build: enable minimumReleaseAge to mitigate dependency chain attacks#13
devversion merged 1 commit intoangular:mainfrom
alan-agius4:min-age

Conversation

@alan-agius4
Copy link
Copy Markdown
Contributor

This change configures pnpm's minimumReleaseAge setting to 1 day (1440 minutes). This is a security measure to mitigate dependency chain attacks, where malicious actors publish a new version of a dependency with malicious code and then trick users into updating to it before it can be discovered and reported.

By delaying the adoption of new releases, we reduce the window of opportunity for such attacks. The list of excluded packages contains trusted and frequently updated dependencies from the Angular team, which are considered safe to use without this delay.

This change configures pnpm's `minimumReleaseAge` setting to 1 day (1440 minutes). This is a security measure to mitigate dependency chain attacks, where malicious actors publish a new version of a dependency with malicious code and then trick users into updating to it before it can be discovered and reported.

By delaying the adoption of new releases, we reduce the window of opportunity for such attacks. The list of excluded packages contains trusted and frequently updated dependencies from the Angular team, which are considered safe to use without this delay.
@devversion devversion merged commit 4132453 into angular:main Sep 17, 2025
3 checks passed
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.

2 participants