@itentialopensource/adapter-venafi_trust_protection_platform
This adapter integrates with system described as: Venafi Trust Protection Platform.
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 dependency; stable pattern across all versions of this adapter package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require uses path.join(__dirname, ...) — resolves to a fixed local file, not user-controlled input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for connectivity/healthcheck utilities in adapter base; consistent with documented adapter framework behavior. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter pattern; preinstall runs a local setup.js utility, not a network fetch or arbitrary shell command. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in utility scripts (setup/migrate), not main adapter code — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; phantom-dep false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dep used in config/connectivity scripts, not directly imported in main code — stable false positive for this adapter pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.8.2 | 15 / 6 | |
| 0.8.0 | 15 / 6 | |
| 0.6.0 | 15 / 6 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.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.
v0.8.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.
v0.8.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.
v0.6.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.