NodeSecure/scanner

AI Summary: Implement two new methods, `fromManifest` and `fromPackument`, in the `ContactExtractor` class to extract contact information from package manifests and packuments respectively, using the `pacote` library and leveraging existing `parseAuthor` functionality from the `utils` workspace. The methods should return raw contact data, leaving parsing to the existing `fromDependencies` method.

AI Summary: Implement a feature in the NodeSecure scanner to flag packages as having external capacity if they use specific HTTP or child_process libraries (like undici, node-fetch, execa, etc.) based on JS-X-Ray reports. This involves modifying the scanner's analysis logic to detect these libraries and set the appropriate flag.

AI Summary: The task is to add a new internationalization (i18n) string, `sast_warnings.sync-io`, to the NodeSecure scanner project. This string will likely be used to warn about synchronous I/O operations in static analysis reports. The related issue suggests this is part of a larger effort to improve the scanner's static analysis capabilities.

AI Summary: The task involves creating comprehensive API documentation for the `@nodesecure/utils` package. This includes generating a README file explaining the functionality of the various functions and classes within the package, likely referencing the TypeScript definitions for accurate descriptions and usage examples.