update imports for [email protected]

[ivegabr]

Description:

This task involves updating the import statements in the rsk-explorer-api project to use the updated [email protected] library. The new version introduces support for both ESM and CommonJS modules and follows modern best practices for module exports. As a result, direct imports from the dist folder are no longer supported or recommended.

The update ensures compatibility with the new version of rsk-utils and aligns with the library's improved structure and API. Once the imports are updated, all functionalities depending on rsk-utils must be thoroughly tested to confirm everything works as expected.

Steps:

1. Replace all instances of direct imports from the dist folder (e.g., @rsksmart/rsk-utils/dist/addresses) with proper imports from the library's public API.

2. Ensure all imports follow the recommended structure, such as:

   import { isAddress } from '@rsksmart/rsk-utils';

3. Test all features and modules in rsk-explorer-api that depend on rsk-utils to verify functionality after the update.

4. Resolve any issues or incompatibilities arising from the library upgrade.

Acceptance Criteria:

• All instances of direct imports from dist in the rsk-explorer-api codebase are replaced with imports from the public API of rsk-utils.
• All features and modules in rsk-explorer-api dependent on rsk-utils are tested and verified to work as expected.
• Unit tests and integration tests pass successfully.
• Code changes align with the updated module system of [email protected].
• Documentation and any relevant comments in the code are updated to reflect the changes.

Impact:

This task ensures that the rsk-explorer-api project uses the latest version of rsk-utils without relying on deprecated or unsupported import paths, improving maintainability and compatibility.

[github-actions]

Dependency Review

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

OpenSSF Scorecard

Package	Version	Score	Details
npm/@rsksmart/rsk-utils	^2.0.5	🟢 8.7	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration CI-Tests 🟢 9 18 out of 19 merged PRs checked by a CI test -- score normalized to 9 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Code-Review 🟢 9 Found 11/12 approved changesets -- score normalized to 9 Contributors 🟢 6 project has 2 contributing companies or organizations -- score normalized to 6 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 29 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 Packaging 🟢 10 packaging workflow detected Pinned-Dependencies 🟢 6 dependency not pinned by hash detected -- score normalized to 6 SAST 🟢 9 SAST tool detected but not run on all commits Security-Policy 🟢 10 security policy file detected Signed-Releases ⚠️ -1 no releases found Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Vulnerabilities 🟢 10 0 existing vulnerabilities detected

Scanned Files

• package.json

[ivegabr]

do not merge until [email protected] is published.

[ivegabr]