@itentialopensource/adapter-google_drive
This adapter integrates with system described as: google drive
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:mocha-param | AI (dependencies): mocha-param is a test-only dependency used across Itential adapter packages; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Itential publishes from GitLab CI without Sigstore provenance; consistent across all their adapter versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Standard Itential adapterBase.js pattern; execSync/spawnSync used for framework utility operations. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): Used in adapter config/connectivity scripts, not directly imported in main code. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter framework setup script; consistent across all adapter versions. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): Test dependency referenced in mocha config files, not directly imported. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Used in adapter utility scripts, not directly imported in main code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Itential adapter framework pattern; dynamic requires load known local modules, not user-supplied paths. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 16 / 6 | |
| 1.0.2 | 16 / 6 | |
| 1.0.1 | 16 / 6 | |
| 1.0.0 | 16 / 6 | |
| 0.11.1 | 16 / 6 | |
| 0.11.0 | 16 / 6 | |
| 0.9.1 | 16 / 6 | |
| 0.9.0 | 16 / 6 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.
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.11.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.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.9.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.9.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.