@itentialopensource/adapter-pitney_bowes
This adapter integrates with system described as: Pitney Bowes.
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): Standard Itential adapter setup script pattern; consistent across all versions of this adapter family. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in Itential adapter base class is a structural framework pattern, not arbitrary code loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapterBase.js for connectivity/healthcheck tooling; consistent with Itential adapter framework design. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in connectivity scripts referenced in config, not directly imported in main code. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in setup/utility scripts, not main adapter code. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test dependency referenced in test config files, not imported in main code. | ai |
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.