@itentialopensource/adapter-tiger_connect
This adapter integrates with system described as: tigerconnect.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:mocha-param | AI (dependencies): mocha-param is a test utility pinned to 2.0.1; stable pattern across Itential adapter versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require uses path.join(__dirname, ...) with a static string — not user-controlled; stable adapter framework pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapter base utilities (execSync/spawnSync); standard for Itential adapter tooling. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter preinstall pattern; runs local utils/setup.js, consistent across all versions. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts declared as runtime dep for interactive setup scripts; stable false positive for this adapter. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param used in test config files; phantom-dep heuristic fires because it's not directly imported in source. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dep used in adapter connectivity checks; referenced in config/scripts. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.0.3 | 15 / 6 | |
| 4.0.1 | 15 / 6 | |
| 4.0.0 | 15 / 6 | |
| 3.6.3 | 15 / 6 | |
| 3.6.2 | 15 / 6 | |
| 3.4.1 | 15 / 6 | |
| 3.4.0 | 15 / 6 |
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.