📦 Scheduled Package Validation Report - Mon Sep 14 2026 - 1 failures

# 📦 Scheduled Package Validation Report - Mon Sep 14 2026

📊 **Summary:**
- Total Components: 3398
- ✅ Validated: 3396
- ❌ Failed: 1
- ⏭️ Skipped: 1
- 📈 Publishable: 3397
- 📉 Failure Rate: 0.03%

## 🔗 Links
- **Workflow Run**: [#69](https://github.com/PipedreamHQ/pipedream/actions/runs/34853310354)
- **Download Reports**: Check the workflow artifacts for detailed JSON and text reports

## ❌ Failed Packages
- **@pipedream/elastic_security** (elastic_security): packageDependencies

## 📋 Failure Categories

### 🔍 PACKAGEDEPENDENCIES Failures (1)
- **@pipedream/elastic_security**: Package imports require corresponding dependencies. Missing dependencies: @pipedream/platform (for import { axios } from "@pipedream/platform")

## 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:
```bash
npm run validate:package --
```

To run validation on all packages:
```bash
npm run validate:packages:verbose
```

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

Start with the @pipedream/elastic_security package and inspect its package.json configuration and imports for the reported @pipedream/platform dependency. Use the workflow artifacts for the detailed report, then run npm run validate:package -- . Done means the package declares its required dependency and passes package validation.

Written by the indexing model from the issue text.