@itentialopensource/adapter-tmf642_alarm_management
This adapter integrates with system described as: tmf642 alarm management.
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): Itential adapter with 35 versions and trusted publisher org; dormancy reflects product release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:mocha-param | AI (dependencies): mocha-param is a test utility dependency stable across this adapter family; low runtime risk. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in adapter tooling utilities (execSync/spawnSync); consistent with Itential adapter framework design. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup script pattern; stable across all versions of this adapter family. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): Referenced in config/test files; stable false positive for this adapter package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Adapter framework pattern for loading adapterBase.js; not arbitrary user-controlled input. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.3 | 15 / 6 | |
| 2.0.2 | 15 / 6 | |
| 2.0.1 | 15 / 6 | |
| 2.0.0 | 15 / 6 |
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.