Add dgvj-work/dbt_dqscore to hub index

[dgvj-work]

Package

• Package URL: https://github.com/dgvj-work/dbt_dqscore
• License: MIT (public repository)
• require-dbt-version: [">=1.3.0", "<3.0.0"]
• Releases: 0.1.0 through 0.1.6 (GitHub Releases + semver tags)
• CI: DuckDB and Postgres integration tests passing
• Scope: Macro-only package (no models); scoring on-run-end hook plus 34 generic data quality tests

Maintenance note: 0.1.6 hardens docs and scoring config (no double hook, string-safe enabled, portable column-count SQL, git install until Hub lists the package). Continuing production use; planning to request another look around Aug 20.

package-best-practices checklist

Real world usage

Using coding agents to help you build your package is totally fine, but please don't submit it to the package hub until you've used it in your own production environment for an extended period of time.

• (Required): I have been using this package in production and am satisfied with its behavior.

First run experience

• MIT license file detectable by GitHub
• README with getting started and customization
• README documents supported warehouses / adapters

Customisability

• No hard-coded table references in package models (macro-only; no models)
• Variables to enable/configure scoring behavior

Dependencies

• require-dbt-version declared in dbt_project.yml
• Range allows subsequent minor/patch releases within supported majors
• No pinned patch-only package dependencies

Interoperability

• Does not override dbt Core behavior for unrelated project resources
• Uses cross-database macros where applicable (e.g. dbt.type_string())
• Resource names disambiguated (dqscore_* tables/macros)

Releases and updates

• Semver git tags (0.1.0 through 0.1.6) with matching GitHub Releases
• Follows SemVer 2.0.0 (pre-1.0 acceptable for early release)

[dbeatty10]

@dgvj-work thanks for submitting! We're asking for submissions to be used in your own production environment for an extended period of time before we share on the dbt Package Hub.

Could you add this portion to the checklist above and let us know when you'd like another review?

[dgvj-work]

Thanks @dbeatty10 - added the Real world usage checklist above.

We've already been using this in production. I'm planning to release an update soon; feel free to take another look around Aug 20.

[dgvj-work]

Hi @dbeatty10, following up as mentioned. We've continued using dbt_dqscore in production since the last update.

Since 0.1.6 we shipped a few patch releases worth noting for review:

• 0.1.7-0.1.9: Snowflake run_completed_at insert fix (to_timestamp_ntz, matching dbt-snowflake snapshot behavior)
• 0.1.8: CI hygiene checks + dbt parse on DuckDB and Postgres
• 0.1.9 is the current release: https://github.com/dgvj-work/dbt_dqscore/releases/tag/0.1.9

CI remains green on DuckDB and Postgres. Happy to adjust anything else on the checklist if needed.

Would appreciate another look when you have time. Thank you.