← Home

@itentialopensource/adapter-sharepoint

This adapter integrates with system described as: sharepoint.

2
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 PlatformAutomationIntegrationAdaptersharepointPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Itential adapter framework pattern; preinstall runs setup.js for adapter scaffolding, consistent across all Itential adapters. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in adapter.js loads adapterBase.js via path.join — deterministic path construction, not user-controlled input. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapterBase.js for adapter utility operations; standard Itential adapter-utils framework pattern. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity/healthcheck utility scripts referenced in package.json scripts, not directly imported in main code. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive utility scripts (setup.js, tbScript.js), not main adapter code. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param is a test runner plugin referenced in test config files, not directly imported. ai

Versions (showing 2 of 2)

Version Deps Published
1.0.1 15 / 6
1.0.0 15 / 6

v1.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.