← Home

@itentialopensource/adapter-starburst

npm Repository Homepage

This adapter integrates with system described as: starburst.

7
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 PlatformAutomationIntegrationAdapterstarburstPre-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 helper dependency; stable pattern across Itential adapter versions. ai
phantom-deps phantom-dep:ping AI (phantom-deps): Used in config/test files; stable false positive for this adapter pattern. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Used in config/test files; stable false positive for this adapter pattern. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): Used in test config files; stable false positive for this adapter pattern. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require resolves known local paths (adapterBase.js etc.) in the Itential adapter framework; not arbitrary user input. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used for adapter health checks and connectivity tests; documented pattern in Itential adapter framework. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup script pattern; stable across all versions of this package family. ai

Versions (showing 7 of 7)

Version Deps Published
1.0.3 15 / 6
1.0.1 15 / 6
0.6.3 15 / 6
0.6.2 15 / 6
0.6.0 15 / 6
0.5.0 15 / 6
0.4.0 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.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.6.2

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

v0.5.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.

v0.4.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.