@activepieces/piece-drupal
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Validation library used in piece configuration; stable false positive. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): HTTP client for Drupal API calls; stable false positive. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Utility dependency for ID generation; stable false positive. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Version utility for Drupal compatibility; stable false positive. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Content-type handling for API requests; stable false positive. | ai | |
| phantom-deps | phantom-dep:axios-retry | AI (phantom-deps): Retry logic for HTTP requests; stable false positive. | ai | |
| phantom-deps | phantom-dep:deepmerge-ts | AI (phantom-deps): Configuration merging utility; stable false positive. | ai | |
| phantom-deps | phantom-dep:@sinclair/typebox | AI (phantom-deps): Schema validation library; stable false positive. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.1.6 | 4 / 0 | |
| 1.1.4 | 12 / 0 | |
| 1.1.3 | 13 / 0 | |
| 1.1.2 | 13 / 0 | |
| 1.1.1 | 13 / 0 | |
| 1.1.0 | 11 / 0 | |
| 1.0.3 | 10 / 0 | |
| 1.0.2 | 9 / 0 | |
| 1.0.1 | 9 / 0 | |
| 1.0.0 | 9 / 0 |
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.