← Home

@itentialopensource/adapter-oracle_assure1

This adapter integrates with system described as: Oracle Assure1

5
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 PlatformAutomationIntegrationAdapteroracle_assure1Pre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:mocha-param AI (dependencies): mocha-param is a test-only helper used across Itential adapter packages; stable false positive for this package family. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in adapter.js loads adapterBase.js via path.join — standard Itential adapter pattern, not arbitrary module loading. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapterBase.js for adapter framework utilities; stable pattern across all Itential adapters. ai
install-scripts install-script:preinstall AI (install-scripts): Itential adapter framework standard setup hook; runs node utils/setup.js, consistent across all adapter versions. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive utility scripts (utils/), 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
phantom-deps phantom-dep:ping AI (phantom-deps): ping is a declared runtime dep used in connectivity/healthcheck scripts, not directly imported in main code. ai

Versions (showing 5 of 5)

Version Deps Published
1.0.3 15 / 6
1.0.1 15 / 6
0.6.4 15 / 6
0.6.3 15 / 6
0.4.1 15 / 6

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

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.

v0.6.4

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.

v0.6.3

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.

v0.4.1

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.