Commitment to the Singer Community
All taps and targets are pulled from external sources, such as GitHub and GitLab, and are organized into a clean YAML format that has no references to external tools. Learn more about the architecture of MeltanoHub for Singer here.
Each tap and target is defined in YAML and is validated against a JSON Schema available via the Hub API.
Each connector page lists revelant information about the maintainer of the connector along with its maintenance status.
Additionally, metrics such as last update, stars, and open issues and PRs, are pulled from GitHub. These are useful proxy metrics for the quality of a given connector.
A listing of all taps and targets is available via the API as JSON. The latest version of these files will always be available at these endpoints:
These files will also be versioned when changes are made in a backwards-incompatible way. The versioned files will be available through the API. Individual YAML files are also available through the individual connector pages or on the repository building MeltanoHub.
Our expectation is that other tools, including Meltano, will utilize the data available via the API to build their own library of Singer taps and targets.
Tap and Target SDKs
Read more about the launch of the SDK on the Meltano blog.
We’ve created a simplified version of the Singer Specification with the goal of making it easier for people new to the Singer ecosystem to understand the spec.
MeltanoHub is built with every part of the Singer ecosystem and Meltano product family. This is a completely open source, end-to-end, production example of Meltano using full-featured Singer connectors.
We use Meltano itself to pull data from GitHub. View the Meltano project for this effort in the Hub repository.
We’re using dbt to manage transformations with Athena to aid in curating the data.