@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, so a manually published version cannot be tied back to a reviewed commit.
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 100 of 423)
| Version | Deps | Published |
|---|---|---|
| 0.10.25 | 4 / 0 | |
| 0.10.24 | 4 / 0 | |
| 0.10.23 | 4 / 0 | |
| 0.10.22 | 4 / 0 | |
| 0.10.21 | 4 / 0 | |
| 0.10.20 | 4 / 0 | |
| 0.10.19 | 4 / 0 | |
| 0.10.18 | 4 / 0 | |
| 0.10.17 | 4 / 0 | |
| 0.10.16 | 4 / 0 | |
| 0.10.15 | 4 / 0 | |
| 0.10.14 | 4 / 0 | |
| 0.10.13 | 4 / 0 | |
| 0.10.12 | 4 / 0 | |
| 0.10.11 | 4 / 0 | |
| 0.10.10 | 4 / 0 | |
| 0.10.9 | 4 / 0 | |
| 0.10.8 | 4 / 0 | |
| 0.10.7 | 4 / 0 | |
| 0.10.6 | 4 / 0 | |
| 0.10.5 | 4 / 0 | |
| 0.10.4 | 4 / 0 | |
| 0.10.3 | 4 / 0 | |
| 0.10.2 | 4 / 0 | |
| 0.10.1 | 4 / 0 | |
| 0.10.0 | 4 / 0 | |
| 0.9.0 | 4 / 0 | |
| 0.8.9 | 4 / 0 | |
| 0.8.8 | 4 / 0 | |
| 0.8.7 | 4 / 0 | |
| 0.8.6 | 4 / 0 | |
| 0.8.5 | 4 / 0 | |
| 0.8.4 | 4 / 0 | |
| 0.8.3 | 4 / 0 | |
| 0.8.2 | 4 / 0 | |
| 0.8.1 | 4 / 0 | |
| 0.8.0 | 4 / 0 | |
| 0.7.4 | 4 / 0 | |
| 0.7.3 | 5 / 0 | |
| 0.7.2 | 5 / 0 | |
| 0.7.1 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.5 | 5 / 0 | |
| 0.6.4 | 4 / 0 | |
| 0.6.3 | 4 / 0 | |
| 0.6.2 | 4 / 0 | |
| 0.6.1 | 4 / 0 | |
| 0.6.0 | 4 / 0 | |
| 0.5.11 | 4 / 0 | |
| 0.5.10 | 4 / 0 | |
| 0.5.9 | 4 / 0 | |
| 0.5.8 | 4 / 0 | |
| 0.5.7 | 4 / 0 | |
| 0.5.6 | 4 / 0 | |
| 0.5.5 | 4 / 0 | |
| 0.5.4 | 4 / 0 | |
| 0.5.3 | 4 / 0 | |
| 0.5.2 | 3 / 0 | |
| 0.5.1 | 3 / 0 | |
| 0.5.0 | 3 / 0 | |
| 0.4.0 | 3 / 0 | |
| 0.3.55 | 3 / 0 | |
| 0.3.54 | 3 / 0 | |
| 0.3.53 | 3 / 0 | |
| 0.3.52 | 3 / 0 | |
| 0.3.51 | 3 / 0 | |
| 0.3.50 | 4 / 0 | |
| 0.3.49 | 4 / 0 | |
| 0.3.48 | 4 / 0 | |
| 0.3.47 | 4 / 0 | |
| 0.3.46 | 4 / 0 | |
| 0.3.45 | 4 / 0 | |
| 0.3.44 | 4 / 0 | |
| 0.3.43 | 4 / 0 | |
| 0.3.42 | 4 / 0 | |
| 0.3.41 | 4 / 0 | |
| 0.3.40 | 4 / 0 | |
| 0.3.39 | 4 / 0 | |
| 0.3.38 | 4 / 0 | |
| 0.3.37 | 4 / 0 | |
| 0.3.36 | 4 / 0 | |
| 0.3.35 | 4 / 0 | |
| 0.3.34 | 4 / 0 | |
| 0.3.33 | 4 / 0 | |
| 0.3.32 | 4 / 0 | |
| 0.3.31 | 4 / 0 | |
| 0.3.30 | 4 / 0 | |
| 0.3.29 | 4 / 0 | |
| 0.3.28 | 4 / 0 | |
| 0.3.27 | 4 / 0 | |
| 0.3.26 | 4 / 0 | |
| 0.3.25 | 4 / 0 | |
| 0.3.24 | 4 / 0 | |
| 0.3.23 | 4 / 0 | |
| 0.3.22 | 3 / 0 | |
| 0.3.21 | 3 / 0 | |
| 0.3.20 | 3 / 0 | |
| 0.3.19 | 3 / 0 | |
| 0.3.18 | 3 / 0 | |
| 0.3.17 | 3 / 0 |
v0.10.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
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.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.