@activepieces/piece-attio
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:@ai-sdk/anthropic | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/replicate | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Monorepo shared dep pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:deepmerge-ts | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:@sinclair/typebox | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:axios-retry | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): Monorepo piece package; shared deps declared at package level but resolved via workspace/framework. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Same monorepo shared-dep pattern. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Used for HMAC webhook signature verification via timingSafeEqual — standard security pattern, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo piece package; missing metadata is consistent across the @activepieces ecosystem. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.1.18 | 4 / 0 | |
| 0.1.17 | 4 / 0 | |
| 0.1.16 | 4 / 0 | |
| 0.1.15 | 4 / 0 | |
| 0.1.14 | 4 / 0 | |
| 0.1.13 | 4 / 0 | |
| 0.1.12 | 4 / 0 | |
| 0.1.11 | 4 / 0 | |
| 0.1.10 | 4 / 0 | |
| 0.1.9 | 4 / 0 | |
| 0.1.8 | 4 / 0 | |
| 0.1.7 | 4 / 0 | |
| 0.1.6 | 4 / 0 | |
| 0.1.5 | 4 / 0 | |
| 0.1.4 | 15 / 0 | |
| 0.1.3 | 16 / 0 | |
| 0.1.2 | 16 / 0 | |
| 0.1.1 | 16 / 0 | |
| 0.1.0 | 14 / 0 | |
| 0.0.6 | 12 / 0 | |
| 0.0.5 | 13 / 0 | |
| 0.0.4 | 19 / 0 | |
| 0.0.3 | 18 / 0 | |
| 0.0.2 | 18 / 0 | |
| 0.0.1 | 17 / 0 |
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.