← Home

@itentialopensource/adapter-new_relic

npm Repository Homepage

This adapter integrates with system described as: api.newrelic.com.

6
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 PlatformAutomationIntegrationAdapternew_relicPre-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 used across Itential adapter packages; stable false positive for this package family. ai
semgrep semgrep:dynamic-require AI (semgrep): Adapter framework pattern using path.join for local module loading; not arbitrary user input. ai
semgrep semgrep:child-process-import AI (semgrep): execSync/spawnSync used in adapter base for connectivity/health checks; consistent with Itential adapter framework. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup script; runs local node utility, not a remote fetch. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in setup/migration utilities, not main adapter code. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param is a test utility referenced in test config files, not directly imported in source. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity/healthcheck utilities referenced in config, not directly imported in main code. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.3 15 / 6
1.0.1 15 / 6
1.0.0 15 / 6
0.5.1 15 / 6
0.5.0 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.

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.

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