📦 Scheduled Package Validation Report - Mon Oct 20 2025 - 2 failures

[github-actions]

📦 Scheduled Package Validation Report - Mon Oct 20 2025

📊 Summary:

• Total Components: 3062
• ✅ Validated: 3059
• ❌ Failed: 2
• ⏭️ Skipped: 1
• 📈 Publishable: 3061
• 📉 Failure Rate: 0.07%

🔗 Links

• Workflow Run: #22
• Download Reports: Check the workflow artifacts for detailed JSON and text reports

❌ Failed Packages

• @pipedream/rss (rss): packageDependencies
• @pipedream/verdict_as_a_service (verdict_as_a_service): import

📋 Failure Categories

🔍 PACKAGEDEPENDENCIES Failures (1)

• @pipedream/rss: Package imports require corresponding dependencies. Missing dependencies: axios (for import axios from "axios")

🔍 IMPORT Failures (1)

• @pipedream/verdict_as_a_service: Import test failed: Command failed: node components/verdict_as_a_service/import_test.mjs
  Import failed for @pipedream/verdict_as_a_service: Named export 'ClientCredentialsGrantAuthenticator' not found. The requested module 'gdata-vaas' is a CommonJS module, which may not support all module.exports as named exports.
  CommonJS modules can always be imported via the default export, for example using:

import pkg from 'gdata-vaas';
const { Vaas, VAAS_URL, ClientCredentialsGrantAuthenticator, } = pkg;

Full Report

The complete validation report is available as an artifact in the workflow run.

Next Steps

1. Review the failed packages listed above
2. Check the full validation report artifact for detailed error messages
3. Fix import/dependency issues in failing packages
4. Consider updating package.json configurations
5. Ensure all main files have proper exports

🔧 Quick Commands

To test a specific package locally:

npm run validate:package -- <package-name>

To run validation on all packages:

npm run validate:packages:verbose

---

This issue was automatically created by the scheduled package validation workflow.