@itentialopensource/adapter-pagerduty
This adapter integrates with system described as: pagerdutyApi.
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter framework pattern; preinstall runs local setup.js for hook configuration, not arbitrary remote code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves local adapter framework files via path.join(__dirname,...); stable pattern across all Itential adapters. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter tooling utilities (tbScript, healthcheck, etc.); consistent with Itential adapter framework. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dependency used in adapter connectivity checks via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in adapter setup/migration utilities via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; stable false positive for this adapter framework. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.10.4 | 15 / 6 | |
| 0.10.2 | 15 / 6 |
v1.0.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.
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.10.4
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.10.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.