Contact

Bugs and feature requests

Open an issue at github.com/educlopez/wingtics/issues. For a rendering bug, the useful report names the component, the variant, the connector, and the viewport — those four narrow almost everything down. A reproduction against @wingtics/connector-mock is ideal, because the mock is deterministic and needs no credentials.

Security

Do not open a public issue for a vulnerability. Use GitHub’s private advisory form at Security → Report a vulnerability. The area worth the most scrutiny is @wingtics/next, since it is the piece that holds provider credentials server-side.

Contributing

Read CONTRIBUTING.md first. Pull requests need a changeset when they touch a published package, and the CI gate is pnpm check plus a production smoke run against a real build.

Friction while working in the repository — a confusing command, a lying type, a test that only fails locally — goes in the friction log rather than a normal issue.

No sales channel

There is nothing to buy, so there is no sales contact and no support SLA. If you need Wingtics to do something it does not do, the issue tracker is the whole process. See about for what the project is and is not.