@itentialopensource/adapter-meraki
This adapter integrates with system described as: merakiDashboardApi.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established Itential adapter with 64 versions; publisher has strong track record (454 approved). Dormancy consistent with maintenance cadence. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapterBase.js for connectivity/healthcheck tooling; expected in Itential adapter framework. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in adapterBase.js loads local config/property files by path; not arbitrary user-controlled input. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup script pattern; consistent across all versions of this adapter family. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive setup/migration utilities; referenced in config files, not main module. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test utility referenced in test config; not a direct import in source. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in adapter connectivity utilities; referenced in config/scripts rather than direct import. | ai |
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
v2.0.0
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.