Bump the production-dependencies group in /frontend with 11 updates

[dependabot]

Bumps the production-dependencies group in /frontend with 11 updates:

Package	From	To
@angular/animations	18.2.12	19.0.0
@angular/cdk	18.2.13	19.0.0
@angular/common	18.2.12	19.0.0
@angular/compiler	18.2.12	19.0.0
@angular/core	18.2.12	19.0.0
@angular/forms	18.2.12	19.0.0
@angular/material	18.2.13	19.0.0
@angular/platform-browser	18.2.12	19.0.0
@angular/platform-browser-dynamic	18.2.12	19.0.0
@angular/router	18.2.12	19.0.0
cronstrue	2.51.0	2.52.0

Updates @angular/animations from 18.2.12 to 19.0.0

Release notes

Sourced from @​angular/animations's releases.

v19.0.0

19.0.0 (2024-11-19)

Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger

... (truncated)

Changelog

Sourced from @​angular/animations's changelog.

19.0.0 (2024-11-19)

Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()

... (truncated)

Commits

• 09df589 refactor(core): Migrate all packages with the explicit-standalone-flag sche...
• 84b6896 refactor(platform-server): Add an ssr benchmark setup. (#57647)
• 9dbe6fc refactor: update license text to point to angular.dev (#57901)
• See full diff in compare view

Updates @angular/cdk from 18.2.13 to 19.0.0

Release notes

Sourced from @​angular/cdk's releases.

v19.0.0

19.0.0 "hafnium-hippo" (2024-11-19)

cdk

Commit	Description
	a11y: use native media query for high contrast detection (#29678)
	private: create cdk-visually-hidden style loader (#29757)
	overlay: avoid having to manually load structural styles
	overlay: load structural styles in a cascade layer (#29725)
	portal: remove ComponentFactoryResolver usages (#27427)
	scrolling: adds ngTemplateContextGuard (#27276)
	text-field: avoid having to manually load text field styles
	tree: fix issue where isExpanded wouldn't be set if placed before isExpandable (#29565)
	tree: only handle keyboard events directly from the node (#29861)
	tree: warn if mixed node types are used within the same tree

material

Commit	Description
	checkbox: add new aria properties to MatCheckbox (#29457)
	core: add experimental theme demo (#29636)
	core: add theme-overrides mixin (#29858)
	core: create focus-indicator structural styles loader (#29763)
	core: default to color-scheme theme type (#29907)
	core: deprecate the core mixin (#29906)
	core: rename theme mixin (#29857)
	core: switch system prefix from sys to mat-sys (#29908)
	input: add the ability to interact with disabled inputs (#29574)
	schematics: create v19 core removal schematic (#29768)
	schematics: Switch custom theme schematic to use theme mixin instead of define-theme and add high contrast override mixins (#29642)
	schematics: Update custom theme schematic to work with light-dark and use theme-overrides mixin (#29911)
	tabs: add alignTabs in MatTabsConfig (#29779)
	theming: Disambiguate token names in theme overrides (#29859)
	timepicker: add test harnesses
	timepicker: add timepicker component
	bottom-sheet: add height minHeight maxHeight to config (#29794)
	core: add missing system variables (#29624)
	core: allow optgroup overrides through core-overrides (#29897)
	core: avoid browser inconsistencies when parsing time
	core: avoid having to manually load ripple styles
	core: change ng-add to use mat.theme (#29990)
	core: correctly identify color input (#29909)
	core: delete deprecated APIs (#29651)
	core: drop sanity checks (#29688)
	core: option showing double selected indicator in high contrast mode
	core: remove unused motion system vars (#29920)
	core: rename sys vars from mat-app to mat-sys (#29879)
	core: stop manually instantiating MatRipple directive (#29630)
	core: update prebuilt themes to use mat.theme (#29989)
	datepicker: calendar font tokens not being picked up (#29610)

... (truncated)

Changelog

Sourced from @​angular/cdk's changelog.

19.0.0 "hafnium-hippo" (2024-11-19)

Breaking Changes

cdk

• • Since cdk.high-contrast targets a media query instead of a class, the specificity of the styles it emits is lower than before.
• • The overlay stays are now loaded slightly later than before which can change their specificity. You may have to update any overlay style overrides.

• • Virtual scrolling lists now have proper type checking which can reveal some previously-hidden compilation errors.

  • fix(cdk/scrolling): adds ngTemplateContextGuard

  implements ngTemplateContextGuard for CdkVirtualForOf directive

material

• • The ripples styles are now loaded slightly later than before which can change their specificity. You may have to update any ripple style overrides.
• • mixinColor and CanColor have been removed. Use a host binding instead.
  • mixinDisableRipple and CanDisableRipple have been removed. Use input transforms instead.
  • mixinDisabled and CanDisable have been removed. Use input transforms instead.
  • mixinInitialized and HasInitialized have been removed. Use a Subject that emits in ngOnInit instead.
  • mixinTabIndex and HasTabIndex have been removed. Use input transforms instead.

google-maps

• • The new @​googlemaps/markerclusterer API should be imported instead of the old one. Read more at: https://github.com/googlemaps/js-markerclusterer
  • The MapMarkerClusterer class has been renamed to DeprecatedMapMarkerClusterer.
  • The map-marker-clusterer selector has been changed to deprecated-map-marker-clusterer.

multiple

• • In order for Material to be compatible with recent changes in Sass and upcoming changes in the CSS standard, tokens are now emitted in-place, rather the being hoisted to the top of the selector. As a result, some token overrides might not apply anymore. This is relevant primarily for the cases like @include mat.button-theme($theme); --mat-button-color: red;. It can be resolved by wrapping the overrides with & {}, for example @include mat.button-theme($theme); & { --mat-button-color: red; }.
• • MatButton.ripple is no longer available.
  • MatCheckbox.ripple is no longer available.
  • MatChip.ripple is no longer available.

material-date-fns-adapter

Commit	Type	Description
234e5e0e8	feat	add support for date-fns 4 (#29744)

youtube-player

Commit	Type	Description
09da06b42	fix	ready event not emitting
288598750	fix	startSeconds not applied when using placeholder

google-maps

Commit	Type	Description
1bd976c6a	feat	Add support for some mouse events #29741 (#29747)
a05475e76	feat	deprecate marker cluster component
c70aae15b	feat	implement new marker clusterer
b9deeee85	fix	add schematic to switch to the new clusterer name
a6709497f	fix	expose all clusterer types (#29905)
74c2a081f	fix	resolve CLI errors in ng update schematic (#29947)

material

Commit	Type	Description
9122335b2	feat	checkbox: add new aria properties to MatCheckbox (#29457)
64ed7ca71	feat	core: add experimental theme demo (#29636)
a58e6f671	feat	core: add theme-overrides mixin (#29858)

... (truncated)

Commits

• 2f3cea1 release: cut the v19.0.0 release
• 56834a2 build: update to v19 final (#30045)
• 734f296 docs: fix broken links (#30038)
• 370e6cc release: cut the v19.0.0-rc.3 release
• 05c78af fix(cdk/table): run differ for all columns (#30012)
• 3a4158e refactor(cdk/testing): fix out of sync file (#30021)
• dbcb921 fix(material/menu): handle keyboard events through dispatcher (#29997)
• 5345a87 fix(material/input): preserve aria-describedby set externally
• 5ba9792 fix(material/form-field): avoid touching the DOM on each state change
• 13beab5 release: cut the v19.0.0-rc.2 release
• Additional commits viewable in compare view

Updates @angular/common from 18.2.12 to 19.0.0

Release notes

Sourced from @​angular/common's releases.

v19.0.0

19.0.0 (2024-11-19)

Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger

... (truncated)

Changelog

Sourced from @​angular/common's changelog.

19.0.0 (2024-11-19)

Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()

... (truncated)

Commits

• 7dfb127 refactor: add @__PURE__ next to @pureOrBreakMyCode for improved bundler c...
• da9c0c5 refactor: cleanup initializers that use ctor params (#58349)
• 24c6373 feat(common): add optional rounded transform support in cloudinary image load...
• 4b9accd feat(http): promote withRequestsMadeViaParent to stable. (#58221)
• 13c1306 feat(common): disable keyvalue sorting using null compareFn (#57487)
• 09df589 refactor(core): Migrate all packages with the explicit-standalone-flag sche...
• 08b4a8a docs: move JSDoc below constructor (#57187)
• a36744e docs: move JSDoc before functions (#58087)
• 0eb1c5c docs(common): Minor typo in code example (#58085)
• 84b6896 refactor(platform-server): Add an ssr benchmark setup. (#57647)
• Additional commits viewable in compare view

Updates @angular/compiler from 18.2.12 to 19.0.0

Release notes

Sourced from @​angular/compiler's releases.

v19.0.0

19.0.0 (2024-11-19)

Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger

... (truncated)

Changelog

Sourced from @​angular/compiler's changelog.

19.0.0 (2024-11-19)

Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()

... (truncated)

Commits

• 806a61b fix(compiler): fix multiline selectors (#58681)
• e5d3abb fix(compiler): resolve :host:host-context(.foo) (#58681)
• 80f5695 fix(compiler): transform chained pseudo-selectors (#58681)
• 2be161d fix(compiler): fix :host parsing in pseudo-selectors (#58681)
• 560282a fix(compiler): control flow nodes with root at the end projected incorrectly ...
• 86d8f6b refactor(compiler): trigger hmr load on initialization (#58465)
• abd0da7 refactor(compiler): remove unused field from output AST (#58444)
• b25121e fix(compiler): avoid having to duplicate core environment (#58444)
• 98804fd fix(compiler): add more specific matcher for hydrate never block (#58360)
• c79b62c refactor(core): remove the standalone feature (#58288)
• Additional commits viewable in compare view

Updates @angular/core from 18.2.12 to 19.0.0

Release notes

Sourced from @​angular/core's releases.

v19.0.0

19.0.0 (2024-11-19)

Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger

... (truncated)

Changelog

Sourced from @​angular/core's changelog.

19.0.0 (2024-11-19)

Blog post: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  // To prevent projecting the default fallback content:
  createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

• Errors that are thrown during ApplicationRef.tick will now be rethrown when using TestBed. These errors should be resolved by ensuring the test environment is set up correctly to complete change detection successfully. There are two alternatives to catch the errors:

  • Instead of waiting for automatic change detection to happen, trigger it synchronously and expect the error. For example, a jasmine test could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()

... (truncated)

Commits

• df210a4 refactor(core): mark linkedSignal as developer preview (#58684)
• e6514b9 fix(migrations): do not migrate next calls in template if not an EventEmitter...
• 91a616f refactor(core): add REQUEST, RESPONSE_INIT and REQUEST_CONTEXT tokens (...
• fa1b021 refactor(core): add performance feature flag for incremental hydration (#58658)
• 5fe57d4 fix(core): fixes issues with control flow and incremental hydration (#58644)
• 715caea refactor(migrations): typos in signal migration incompatibility reasons (#58636)
• e26797b fix(migrations): replace removed NgModules in tests with their exports (#58627)
• b84ed2b fix(migrations): include the output migration in the defaults of the signal m...
• a5e7a02 refactor(core): moves incremental hydration codebase to better locations (#58...
• 560282a fix(compiler): control flow nodes with root at the end projected incorrectly ...
• Additional commits viewable in compare view

Updates @angular/forms from 18.2.12 to 19.0.0

Release notes

Sourced from @​angular/forms's releases.

v19.0.0

19.0.0 (2024-11-19)

Explore Angular v19 with a blog post from the Angular team: https://blog.angular.dev/meet-angular-v19-7b29dfd05b84

Breaking Changes

compiler

• this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

• Angular directives, components and pipes are now standalone by default.

  • Specify standalone: false for declarations that are currently declared in @NgModules.
  • ng update for v19 will take care of this automatically.

• TypeScript versions less than 5.5 are no longer supported.

• Timing changes for effect API (in developer preview):

  • effects which are triggered outside of change detection run as part of the change detection process instead of as a microtask. Depending on the specifics of application/test setup, this can result in them executing earlier or later (or requiring additional test steps to trigger; see below examples).

  • effects which are triggered during change detection (e.g. by input signals) run earlier, before the component's template.

• ExperimentalPendingTasks has been renamed to PendingTasks.

• The autoDetect feature of ComponentFixture will now attach the fixture to the ApplicationRef. As a result, errors during automatic change detection of the fixture be reported to the ErrorHandler. This change may cause custom error handlers to observe new failures that were previously unreported.

• createComponent will now render default fallback with empty projectableNodes.

  • When passing an empty array to projectableNodes in the createComponent API, the default fallback content of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

  // The first ng-content will render the default fallback content if present
  createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });
  <...
  Description has been truncated

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Scorecard details

Package	Version	Score	Details
npm/@angular/animations	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/cdk	19.0.0	🟢 7.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 28 out of 28 merged PRs checked by a CI test -- score normalized to 10 CII-Best-Practices ⚠️ 2 badge detected: in_progress Code-Review 🟢 10 all changesets reviewed Contributors 🟢 10 21 different organizations found -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) out of 30 and 4 issue activity out of 30 found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 no published package detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions 🟢 8 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 51 existing vulnerabilities detected
npm/@angular/common	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/compiler	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/core	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/forms	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/material	19.0.0	🟢 7.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 28 out of 28 merged PRs checked by a CI test -- score normalized to 10 CII-Best-Practices ⚠️ 2 badge detected: in_progress Code-Review 🟢 10 all changesets reviewed Contributors 🟢 10 21 different organizations found -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) out of 30 and 4 issue activity out of 30 found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 no published package detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions 🟢 8 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 51 existing vulnerabilities detected
npm/@angular/platform-browser	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/platform-browser-dynamic	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/router	19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/cronstrue	2.52.0	🟢 3.6	Details Check Score Reason Code-Review ⚠️ 2 Found 7/28 approved changesets -- score normalized to 2 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Maintained 🟢 4 3 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 4 Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Security-Policy ⚠️ 0 security policy file not detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Vulnerabilities 🟢 6 4 existing vulnerabilities detected
npm/zone.js	0.15.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/animations	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/cdk	^19.0.0	🟢 7.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 28 out of 28 merged PRs checked by a CI test -- score normalized to 10 CII-Best-Practices ⚠️ 2 badge detected: in_progress Code-Review 🟢 10 all changesets reviewed Contributors 🟢 10 21 different organizations found -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) out of 30 and 4 issue activity out of 30 found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 no published package detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions 🟢 8 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 51 existing vulnerabilities detected
npm/@angular/common	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/compiler	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/core	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/forms	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/material	^19.0.0	🟢 7.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests 🟢 10 28 out of 28 merged PRs checked by a CI test -- score normalized to 10 CII-Best-Practices ⚠️ 2 badge detected: in_progress Code-Review 🟢 10 all changesets reviewed Contributors 🟢 10 21 different organizations found -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) out of 30 and 4 issue activity out of 30 found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 no published package detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions 🟢 8 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 51 existing vulnerabilities detected
npm/@angular/platform-browser	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/platform-browser-dynamic	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/@angular/router	^19.0.0	🟢 6.4	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection 🟢 6 branch protection is not maximal on development and all release branches CI-Tests ⚠️ -1 no pull request found CII-Best-Practices ⚠️ 2 badge detected: InProgress Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Contributors 🟢 10 project has 38 contributing companies or organizations Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Dependency-Update-Tool 🟢 10 update tool detected Fuzzing 🟢 10 project is fuzzed License 🟢 10 license file detected Maintained 🟢 10 30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10 Packaging ⚠️ -1 packaging workflow not detected Pinned-Dependencies 🟢 10 all dependencies are pinned SAST ⚠️ 0 no SAST tool detected Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Vulnerabilities ⚠️ 0 66 existing vulnerabilities detected
npm/cronstrue	^2.52.0	🟢 3.6	Details Check Score Reason Code-Review ⚠️ 2 Found 7/28 approved changesets -- score normalized to 2 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Maintained 🟢 4 3 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 4 Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Security-Policy ⚠️ 0 security policy file not detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Vulnerabilities 🟢 6 4 existing vulnerabilities detected

Scanned Files

• frontend/package-lock.json
• frontend/package.json

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.