@activepieces/piece-ai
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:form-data | AI (phantom-deps): Same monorepo shared-deps pattern. | ai | |
| phantom-deps | phantom-dep:@sinclair/typebox | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:deepmerge-ts | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:axios-retry | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established @activepieces org; no provenance is consistent across all their packages. | ai | |
| phantom-deps | phantom-dep:jose | AI (phantom-deps): Transitive dep explicitly listed; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ms | AI (phantom-deps): Transitive dep of express explicitly listed in package.json; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Transitive dep explicitly listed in package.json. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): Transitive dep of express explicitly listed in package.json. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Package explicitly lists transitive deps of express/hono/ai-sdk; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@hono/node-server | AI (phantom-deps): Explicitly declared transitive dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/gateway | AI (phantom-deps): Explicitly declared transitive dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): Explicitly declared transitive dep; phantom-dep heuristic is a stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo piece package; missing metadata is consistent across the Activepieces piece ecosystem. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes AI-generated image data (base64 image bytes from API response); not an obfuscation pattern. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.4.3 | 19 / 1 | |
| 0.4.2 | 19 / 1 | |
| 0.4.1 | 19 / 1 | |
| 0.4.0 | 19 / 1 | |
| 0.3.9 | 19 / 1 | |
| 0.3.8 | 19 / 1 | |
| 0.3.7 | 19 / 1 | |
| 0.3.6 | 19 / 1 | |
| 0.3.5 | 18 / 1 | |
| 0.3.4 | 111 / 1 | |
| 0.3.3 | 113 / 1 | |
| 0.3.1 | 113 / 1 | |
| 0.3.0 | 18 / 1 | |
| 0.2.0 | 18 / 1 | |
| 0.1.21 | 18 / 1 | |
| 0.1.20 | 18 / 1 | |
| 0.1.19 | 18 / 1 | |
| 0.1.18 | 18 / 1 | |
| 0.1.17 | 18 / 1 | |
| 0.1.16 | 18 / 1 | |
| 0.1.15 | 18 / 1 | |
| 0.1.14 | 18 / 1 | |
| 0.1.13 | 18 / 1 | |
| 0.1.12 | 13 / 0 | |
| 0.1.11 | 13 / 0 | |
| 0.1.10 | 25 / 0 | |
| 0.1.9 | 25 / 0 | |
| 0.1.8 | 25 / 0 | |
| 0.1.7 | 25 / 0 | |
| 0.1.6 | 25 / 0 | |
| 0.1.5 | 25 / 0 | |
| 0.1.4 | 25 / 0 | |
| 0.1.3 | 25 / 0 | |
| 0.1.2 | 25 / 0 | |
| 0.1.1 | 26 / 0 | |
| 0.1.0 | 26 / 0 | |
| 0.0.9 | 25 / 0 | |
| 0.0.8 | 25 / 0 | |
| 0.0.7 | 25 / 0 | |
| 0.0.6 | 22 / 0 | |
| 0.0.5 | 22 / 0 | |
| 0.0.4 | 22 / 0 | |
| 0.0.3 | 22 / 0 | |
| 0.0.2 | 21 / 0 | |
| 0.0.1 | 21 / 0 |
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.