← Home

@itentialopensource/adapter-db_mssql

npm Repository Homepage

Itential adapter to connect to mssql

6
Versions
Apache-2.0
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

jared.obrienjohnpolanskyzack.strulovitchitential-ciandyknaebelishitaprakash

Keywords

ItentialItential PlatformAutomationIntegrationAdapterPersistenceMicrosoftSQLPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup script pattern; consistent across all versions of this package family. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads package.json for version introspection; not arbitrary module loading. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used only in testRunner.js test utility, not in runtime adapter code. ai
phantom-deps phantom-dep:ajv AI (phantom-deps): ajv is a runtime dep used in config validation; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:mocha AI (phantom-deps): mocha listed as runtime dep but used in test scripts; phantom-dep heuristic false positive. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.1 6 / 6
2.0.0 6 / 6
1.3.3 6 / 6
1.3.2 6 / 6
1.3.1 6 / 6
1.3.0 6 / 6

v2.0.1

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.3

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.2

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.1

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.0

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.