Security fixes are released for the latest version only. Update to the newest release to receive them.
| Version | Supported |
|---|---|
| Latest release | ✅ |
| Older releases | ❌ |
If you discover a security vulnerability in this project:
- Do not create a public GitHub issue
- Report via one of the following:
- Preferred: GitHub Security Advisories (report privately)
- Alternative: security@itential.com
- Include in your report:
- Description of the vulnerability
- Steps to reproduce
- Affected versions
- Impact assessment
- Suggested fix (if any)
We will acknowledge your report within 48 hours and provide regular updates on our progress toward a fix. We follow coordinated disclosure practices.
These skills drive an AI agent that calls your Itential Platform's API with your credentials. When using them:
- Credentials: keep platform credentials in the
.envof the folder you work in (the agent caches a token in.auth.jsonnext to it). Never commit either file, and never put credentials in a skill'scustom/rules. - Least privilege: use a service account whose roles cover only what the work needs, rather than an administrator's login.
- Review before changes: read what the agent plans to change on the platform before you approve it, and try new work on a non-production platform first.
- Treat
custom/rules as code: they are instructions the agent follows. Review changes to them like any other change to your automation. - Report skill guidance that is unsafe — for example, guidance that could expose credentials or bypass a skill's safety rules — the same way as any other vulnerability (above).