Angular core version 7.2.14 represents a minor update to the core Angular framework, building upon the foundation established in version 7.2.13. Both versions share the same fundamental characteristics: they are described as the core framework for Angular applications, maintain the same dependencies on tslib (version 1.9.0 or higher), and require peer dependencies of rxjs (version 6.0.0 or higher) and zone.js (version ~0.8.26). Both versions are licensed under the MIT license and are maintained in the Angular GitHub repository. Furthermore, the file count (611) and unpacked size (20728232 bytes) are identical, suggesting that the code changes were relatively small and didn't significantly impact the overall size of the package.
The key difference lies in the release date. Version 7.2.14 was released on April 23, 2019, while 7.2.13 was released on April 13, 2019. This 10-day gap indicates that 7.2.14 likely includes bug fixes, performance improvements, or minor feature enhancements that were not present in 7.2.13. While the specific nature of these changes isn't detailed in the provided data, developers are encouraged to consult the official Angular changelog or release notes for a comprehensive list of modifications.
For developers using Angular, upgrading to the latest minor version (7.2.14 in this case) is generally recommended to benefit from the latest improvements. Since the major and minor versions remain the same, this upgrade is unlikely to introduce breaking changes. Make sure to review the official changelog, do testing, and assess whether there would be a migration path impact in your testing environment before updating.
All the vulnerabilities related to the version 7.2.14 of the package
Cross site scripting in Angular
A vulnerability was found in Angular up to 11.0.4/11.1.0-next.2. It has been classified as problematic. Affected is the handling of comments. The manipulation leads to cross site scripting. It is possible to launch the attack remotely but it might require an authentication first. Upgrading to version 10.2.5, 11.0.5 or 11.1.0-next.3 is advised to to address this issue.