← Browse the extensions catalog

tds-fdw

Source README ↗

Overview

tds_fdw is a PostgreSQL Foreign Data Wrapper (FDW) that enables PostgreSQL to query Microsoft SQL Server and Sybase databases using the TDS (Tabular Data Stream) protocol via FreeTDS.

Package details

Extension version
2.0.5
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Trixie · amd64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION tds_fdw;
SQL version
2.0.5

PostgreSQL parameters

None specified

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-WorkflowUnknown

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no workflows found

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-Protection1

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Warn: branch protection not enabled for branch '1.0'
  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: branch 'master' does not require approvers
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: 'up-to-date branches' is disabled on branch 'master'
  • Info: status check found to merge onto on branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

Check details ↗

Code-Review0

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: Found 1/14 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-PermissionsUnknown

Determines if the project's workflows follow the principle of least privilege.

Reasoning: No tokens found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 0

  • Warn: 0 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests10

Determines if the project runs tests before pull requests are merged.

Reasoning: 14 out of 14 merged PRs checked by a CI test -- score normalized to 10

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: SUSE, cybertec, juliogonzalez-training, openSUSE, scylladb, suse, tds-fdw, uyuni-project

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • BSD-3-Clause AND LicenseRef-Expat AND LicenseRef-GFDL AND LicenseRef-GFDL-NIV-1.1- AND GPL-2.0-only AND GPL-2.0-or-later AND ISC AND LicenseRef-LGPL AND LGPL-2.0-or-later AND LicenseRef-public-domain1 package
  • PostgreSQL1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

2 files read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence

Overview

tds_fdw is a PostgreSQL Foreign Data Wrapper (FDW) that enables PostgreSQL to query Microsoft SQL Server and Sybase databases using the TDS (Tabular Data Stream) protocol via FreeTDS.

Package details

Extension version
2.0.5
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Trixie · arm64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION tds_fdw;
SQL version
2.0.5

PostgreSQL parameters

None specified

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-WorkflowUnknown

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no workflows found

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-Protection1

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Warn: branch protection not enabled for branch '1.0'
  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: branch 'master' does not require approvers
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: 'up-to-date branches' is disabled on branch 'master'
  • Info: status check found to merge onto on branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

Check details ↗

Code-Review0

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: Found 1/14 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-PermissionsUnknown

Determines if the project's workflows follow the principle of least privilege.

Reasoning: No tokens found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 0

  • Warn: 0 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests10

Determines if the project runs tests before pull requests are merged.

Reasoning: 14 out of 14 merged PRs checked by a CI test -- score normalized to 10

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: SUSE, cybertec, juliogonzalez-training, openSUSE, scylladb, suse, tds-fdw, uyuni-project

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • BSD-3-Clause AND LicenseRef-Expat AND LicenseRef-GFDL AND LicenseRef-GFDL-NIV-1.1- AND GPL-2.0-only AND GPL-2.0-or-later AND ISC AND LicenseRef-LGPL AND LGPL-2.0-or-later AND LicenseRef-public-domain1 package
  • PostgreSQL1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

2 files read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence

Overview

tds_fdw is a PostgreSQL Foreign Data Wrapper (FDW) that enables PostgreSQL to query Microsoft SQL Server and Sybase databases using the TDS (Tabular Data Stream) protocol via FreeTDS.

Package details

Extension version
2.0.5
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Bookworm · amd64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION tds_fdw;
SQL version
2.0.5

PostgreSQL parameters

None specified

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-WorkflowUnknown

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no workflows found

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-Protection1

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Warn: branch protection not enabled for branch '1.0'
  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: branch 'master' does not require approvers
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: 'up-to-date branches' is disabled on branch 'master'
  • Info: status check found to merge onto on branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

Check details ↗

Code-Review0

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: Found 1/14 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-PermissionsUnknown

Determines if the project's workflows follow the principle of least privilege.

Reasoning: No tokens found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 0

  • Warn: 0 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests10

Determines if the project runs tests before pull requests are merged.

Reasoning: 14 out of 14 merged PRs checked by a CI test -- score normalized to 10

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: SUSE, cybertec, juliogonzalez-training, openSUSE, scylladb, suse, tds-fdw, uyuni-project

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • BSD-3-Clause AND LicenseRef-Expat AND LicenseRef-GFDL AND LicenseRef-GFDL-NIV-1.1- AND GPL-2.0-only AND GPL-2.0-or-later AND ISC AND LicenseRef-LGPL AND LGPL-2.0-or-later AND LicenseRef-public-domain1 package
  • PostgreSQL1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

2 files read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence

Overview

tds_fdw is a PostgreSQL Foreign Data Wrapper (FDW) that enables PostgreSQL to query Microsoft SQL Server and Sybase databases using the TDS (Tabular Data Stream) protocol via FreeTDS.

Package details

Extension version
2.0.5
Image built
Publisher
cnpg-extensions
Build
Debian
Platform
PG 18 · Bookworm · arm64

Project links

Links from package metadata, recipe update rules, or reviewed upstream mappings.

Database setup

Required extensions
None specified
SQL installation
CREATE EXTENSION tds_fdw;
SQL version
2.0.5

PostgreSQL parameters

None specified

These recipe settings are used in automated smoke tests.

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software.

View information about checks. Automated results are informational only; some categories may not apply to this project.

Scanned · Download cached scan ↓

Dangerous-WorkflowUnknown

Determines if the project's GitHub Action workflows avoid dangerous patterns.

Reasoning: no workflows found

Check details ↗

Binary-Artifacts10

Determines if the project has generated executable (binary) artifacts in the source repository.

Reasoning: no binaries found in the repo

Check details ↗

Branch-Protection1

Determines if the default and release branches are protected with GitHub's branch protection settings.

Reasoning: branch protection is not maximal on development and all release branches

  • Warn: branch protection not enabled for branch '1.0'
  • Info: 'allow deletion' disabled on branch 'master'
  • Info: 'force pushes' disabled on branch 'master'
  • Warn: 'branch protection settings apply to administrators' is disabled on branch 'master'
  • Warn: 'stale review dismissal' is disabled on branch 'master'
  • Warn: branch 'master' does not require approvers
  • Warn: codeowners review is not required on branch 'master'
  • Warn: 'last push approval' is disabled on branch 'master'
  • Warn: 'up-to-date branches' is disabled on branch 'master'
  • Info: status check found to merge onto on branch 'master'
  • Info: PRs are required in order to make changes on branch 'master'

Check details ↗

Code-Review0

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

Reasoning: Found 1/14 approved changesets -- score normalized to 0

Check details ↗

Dependency-Update-Tool0

Determines if the project uses a dependency update tool.

Reasoning: no update tool detected

  • Warn: no dependency update tool configurations found

Check details ↗

Maintained0

Determines if the project is "actively maintained".

Reasoning: 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Check details ↗

Token-PermissionsUnknown

Determines if the project's workflows follow the principle of least privilege.

Reasoning: No tokens found

Check details ↗

Vulnerabilities10

Determines if the project has open, known unfixed vulnerabilities.

Reasoning: 0 existing vulnerabilities detected

Check details ↗

Fuzzing0

Determines if the project uses fuzzing.

Reasoning: project is not fuzzed

  • Warn: no fuzzer integrations found

Check details ↗

Pinned-DependenciesUnknown

Determines if the project has declared and pinned the dependencies of its build process.

Reasoning: no dependencies found

Check details ↗

SAST0

Determines if the project uses static code analysis.

Reasoning: SAST tool is not run on all commits -- score normalized to 0

  • Warn: 0 commits out of 30 are checked with a SAST tool

Check details ↗

Security-Policy0

Determines if the project has published a security policy.

Reasoning: security policy file not detected

  • Warn: no security policy file detected
  • Warn: no security file to analyze
  • Warn: no security file to analyze
  • Warn: no security file to analyze

Check details ↗

CI-Tests10

Determines if the project runs tests before pull requests are merged.

Reasoning: 14 out of 14 merged PRs checked by a CI test -- score normalized to 10

Check details ↗

CII-Best-Practices0

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

Reasoning: no effort to earn an OpenSSF best practices badge detected

Check details ↗

Contributors10

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

Reasoning: project has 8 contributing companies or organizations

  • Info: found contributions from: SUSE, cybertec, juliogonzalez-training, openSUSE, scylladb, suse, tds-fdw, uyuni-project

Check details ↗

License9

Determines if the project has defined a license.

Reasoning: license file detected

  • Info: project has a license file: LICENSE:0
  • Warn: project license file does not contain an FSF or OSI license.

Check details ↗

Extension recipe
PostgreSQL

License expressions in the shipped package inventory

  • BSD-3-Clause AND LicenseRef-Expat AND LicenseRef-GFDL AND LicenseRef-GFDL-NIV-1.1- AND GPL-2.0-only AND GPL-2.0-or-later AND ISC AND LicenseRef-LGPL AND LGPL-2.0-or-later AND LicenseRef-public-domain1 package
  • PostgreSQL1 package

Expressions retain AND / OR terms. A package may appear under more than one expression. LicenseRef names refer to custom terms.

Image license files

View files →

2 files read directly from /licenses in the selected image. Browse their original contents and checksums in the Licenses tab.

Evidence