@itentialopensource/adapter-fortimanager
This adapter integrates with system described as: fortimanager
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): Long-lived Itential adapter with 40 versions; publisher has 454 approved packages and no material changes in this release. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Adapter framework module-loading pattern; path.join(__dirname, ...) is safe relative-path resolution, not arbitrary input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used for adapter utility scripts (migration, healthcheck); standard in Itential adapter base class. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter pattern; preinstall runs setup.js for git hooks/migration, consistent across all org adapters. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive CLI utility scripts, not main module import. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; phantom-dep false positive for test tooling. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in connectivity/healthcheck utility scripts, not directly imported in main module. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.12.4 | 15 / 6 | |
| 0.12.2 | 15 / 6 | |
| 0.12.0 | 15 / 6 | |
| 0.11.0 | 15 / 6 | |
| 0.10.1 | 15 / 6 | |
| 0.10.0 | 15 / 6 |
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.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.
v0.12.4
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.
v0.12.2
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.
v0.12.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.
v0.11.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.
v0.10.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.
v0.10.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.