We actively support the following versions with security updates:
| Version | Supported |
|---|---|
| Latest | ✅ |
| < Latest | ❌ |
If you discover a security vulnerability, please report it responsibly:
- Do not open a public GitHub issue
- Email the maintainers directly (if contact info is available)
- Use GitHub's Security Advisory feature for private disclosure
- Include as much detail as possible about the vulnerability
- Always use the latest version of this library
- Keep Go updated to the latest stable version
- Validate all API responses before processing
- Use HTTPS for all API communications
- Store API tokens securely (environment variables, secret management systems)
- Implement proper timeout configurations for HTTP clients
- Use rate limiting to prevent API abuse
package main
import (
"context"
"net/http"
"time"
"github.com/kothar/asana-go"
)
func main() {
// Create HTTP client with security-focused configuration
httpClient := &http.Client{
Timeout: 30 * time.Second,
Transport: &http.Transport{
MaxIdleConns: 10,
IdleConnTimeout: 30 * time.Second,
DisableCompression: false,
TLSHandshakeTimeout: 10 * time.Second,
},
}
client := asana.NewClient(httpClient)
// Use the client...
}This project uses Go modules for dependency management. We regularly update dependencies to address security vulnerabilities.
- Automated vulnerability scanning with
govulncheck - Dependency vulnerability scanning with Trivy
- GitHub Security Advisories enabled
- Regular dependency updates
The project includes automated security scanning in CI/CD:
- govulncheck: Scans for known vulnerabilities in Go dependencies
- Trivy: Multi-purpose security scanner for vulnerabilities and misconfigurations
- gosec: Static analysis tool for Go security issues
- 2025-01: Updated Go to 1.24.4 to address standard library vulnerabilities (GO-2025-3751, GO-2025-3750, GO-2025-3749)
- 2025-01: Updated golang.org/x/oauth2 to v0.30.0 to address memory consumption vulnerability (GO-2025-3488)
- 2025-01: Enhanced CI/CD pipeline with comprehensive security scanning
For security-related questions or concerns, please:
- Check existing GitHub Security Advisories
- Review this security policy
- Contact the maintainers through appropriate channels
We appreciate security researchers who responsibly disclose vulnerabilities. All verified security issues will be acknowledged in our security changelog.