@activepieces/shared
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:ms | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:yallist | AI (phantom-deps): Transitive dependency of lru-cache; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): Declared and used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:engine.io-client | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:engine.io-parser | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:socket.io-client | AI (phantom-deps): Declared and used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:socket.io-parser | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:xmlhttprequest-ssl | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@socket.io/component-emitter | AI (phantom-deps): Transitive dependency of socket.io-client; stable pattern for this package. | ai |
Versions (showing 52 of 156)
| Version | Deps | Published |
|---|---|---|
| 0.20.1 | 5 / 0 | |
| 0.20.0 | 5 / 0 | |
| 0.19.1 | 5 / 0 | |
| 0.19.0 | 5 / 0 | |
| 0.18.6 | 11 / 0 | |
| 0.18.5 | 11 / 0 | |
| 0.18.4 | 11 / 0 | |
| 0.18.3 | 11 / 0 | |
| 0.18.2 | 11 / 0 | |
| 0.18.1 | 11 / 0 | |
| 0.18.0 | 10 / 0 | |
| 0.17.12 | 11 / 0 | |
| 0.17.11 | 10 / 0 | |
| 0.17.10 | 10 / 0 | |
| 0.17.9 | 10 / 0 | |
| 0.17.8 | 10 / 0 | |
| 0.17.7 | 10 / 0 | |
| 0.17.6 | 10 / 0 | |
| 0.17.5 | 10 / 0 | |
| 0.17.4 | 10 / 0 | |
| 0.17.3 | 10 / 0 | |
| 0.17.2 | 10 / 0 | |
| 0.17.1 | 10 / 0 | |
| 0.17.0 | 10 / 0 | |
| 0.16.0 | 10 / 0 | |
| 0.15.2 | 10 / 0 | |
| 0.15.1 | 10 / 0 | |
| 0.15.0 | 10 / 0 | |
| 0.14.6 | 10 / 0 | |
| 0.14.5 | 10 / 0 | |
| 0.14.4 | 10 / 0 | |
| 0.14.3 | 10 / 0 | |
| 0.14.2 | 10 / 0 | |
| 0.14.1 | 10 / 0 | |
| 0.13.3 | 9 / 0 | |
| 0.13.2 | 9 / 0 | |
| 0.13.1 | 9 / 0 | |
| 0.13.0 | 9 / 0 | |
| 0.12.0 | 5 / 0 | |
| 0.11.5 | 5 / 0 | |
| 0.11.4 | 5 / 0 | |
| 0.11.3 | 5 / 0 | |
| 0.11.2 | 5 / 0 | |
| 0.11.1 | 5 / 0 | |
| 0.11.0 | 5 / 0 | |
| 0.10.178 | 5 / 0 | |
| 0.10.177 | 5 / 0 | |
| 0.10.176 | 5 / 0 | |
| 0.10.175 | 5 / 0 | |
| 0.10.174 | 5 / 0 | |
| 0.10.173 | 5 / 0 | |
| 0.10.172 | 5 / 0 |
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.