@nestjs/common versions 11.0.3 and 11.0.2 present minimal differences, primarily distinguished by their release dates. Both versions share identical descriptions, dependencies (uid 2.0.2, tslib 2.8.1, iterare 1.2.1), peer dependencies (rxjs ^7.1.0, class-validator *, reflect-metadata ^0.1.12 || ^0.2.0, class-transformer *), license (MIT), repository, author, funding information, file count (397), and unpacked size (453247). The sole distinction lies in their release timestamps, with version 11.0.3 released on "2025-01-20T11:37:22.692Z" versus 11.0.2 on "2025-01-20T08:14:22.531Z".
For developers using @nestjs/common, this information suggests that upgrading from 11.0.2 to 11.0.3 is unlikely to introduce any breaking changes or new features. The update likely involves minor bug fixes, performance improvements, or documentation updates that don't significantly impact the API or core functionality. Therefore, if a project is running smoothly on 11.0.2, upgrading to 11.0.3 could be considered a routine maintenance task to ensure access to the latest patches. Developers should always consult the official changelog or release notes for a comprehensive understanding of the specific changes included in the new version, although based on the identical metadata, the changes are probably very small.
All the vulnerabilities related to the version 11.0.3 of the package
nest allows a remote attacker to execute arbitrary code via the Content-Type header
File Upload vulnerability in nestjs nest prior to v.11.0.16 allows a remote attacker to execute arbitrary code via the Content-Type header.
