@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 100 of 147)
| Version | Deps | Published |
|---|---|---|
| 0.86.0 | 9 / 3 | |
| 0.85.0 | 9 / 3 | |
| 0.83.0 | 9 / 3 | |
| 0.82.2 | 9 / 3 | |
| 0.82.1 | 9 / 3 | |
| 0.82.0 | 9 / 3 | |
| 0.81.1 | 9 / 3 | |
| 0.81.0 | 9 / 3 | |
| 0.80.1 | 9 / 3 | |
| 0.80.0 | 8 / 3 | |
| 0.79.0 | 8 / 3 | |
| 0.78.1 | 8 / 3 | |
| 0.78.0 | 8 / 3 | |
| 0.77.1 | 8 / 3 | |
| 0.77.0 | 8 / 3 | |
| 0.76.9 | 8 / 3 | |
| 0.76.8 | 8 / 3 | |
| 0.76.7 | 8 / 3 | |
| 0.76.6 | 8 / 3 | |
| 0.76.4 | 8 / 3 | |
| 0.76.3 | 8 / 3 | |
| 0.76.2 | 8 / 3 | |
| 0.76.1 | 8 / 3 | |
| 0.76.0 | 8 / 3 | |
| 0.75.0 | 8 / 3 | |
| 0.74.0 | 8 / 3 | |
| 0.73.0 | 8 / 3 | |
| 0.72.1 | 8 / 3 | |
| 0.72.0 | 8 / 3 | |
| 0.71.7 | 8 / 3 | |
| 0.71.6 | 8 / 3 | |
| 0.71.5 | 8 / 3 | |
| 0.71.4 | 8 / 3 | |
| 0.71.3 | 8 / 3 | |
| 0.71.2 | 8 / 3 | |
| 0.71.1 | 8 / 3 | |
| 0.70.1 | 8 / 3 | |
| 0.69.0 | 8 / 3 | |
| 0.68.6 | 8 / 3 | |
| 0.68.5 | 8 / 3 | |
| 0.68.4 | 8 / 3 | |
| 0.68.3 | 8 / 3 | |
| 0.68.2 | 8 / 3 | |
| 0.68.1 | 8 / 3 | |
| 0.67.1 | 8 / 3 | |
| 0.67.0 | 8 / 3 | |
| 0.66.1 | 8 / 3 | |
| 0.66.0 | 8 / 3 | |
| 0.65.0 | 8 / 3 | |
| 0.64.0 | 18 / 3 | |
| 0.62.0 | 17 / 3 | |
| 0.61.0 | 17 / 3 | |
| 0.60.0 | 17 / 3 | |
| 0.58.3 | 17 / 3 | |
| 0.58.2 | 17 / 3 | |
| 0.58.0 | 17 / 3 | |
| 0.57.2 | 17 / 3 | |
| 0.57.1 | 17 / 3 | |
| 0.57.0 | 17 / 3 | |
| 0.55.2 | 17 / 3 | |
| 0.55.1 | 17 / 3 | |
| 0.54.4 | 17 / 3 | |
| 0.54.3 | 17 / 3 | |
| 0.54.2 | 17 / 3 | |
| 0.54.1 | 17 / 3 | |
| 0.54.0 | 7 / 3 | |
| 0.53.2 | 7 / 3 | |
| 0.53.1 | 7 / 3 | |
| 0.53.0 | 7 / 3 | |
| 0.51.8 | 7 / 3 | |
| 0.51.7 | 7 / 3 | |
| 0.51.6 | 7 / 3 | |
| 0.51.4 | 7 / 3 | |
| 0.51.2 | 7 / 3 | |
| 0.51.1 | 7 / 3 | |
| 0.51.0 | 7 / 3 | |
| 0.50.1 | 7 / 3 | |
| 0.50.0 | 7 / 3 | |
| 0.49.1 | 7 / 3 | |
| 0.30.1 | 6 / 0 | |
| 0.30.0 | 6 / 0 | |
| 0.29.0 | 6 / 0 | |
| 0.28.0 | 6 / 0 | |
| 0.27.0 | 6 / 0 | |
| 0.26.2 | 6 / 0 | |
| 0.26.1 | 6 / 0 | |
| 0.26.0 | 6 / 0 | |
| 0.25.2 | 5 / 0 | |
| 0.25.1 | 5 / 0 | |
| 0.25.0 | 5 / 0 | |
| 0.24.1 | 5 / 0 | |
| 0.24.0 | 5 / 0 | |
| 0.23.0 | 5 / 0 | |
| 0.22.0 | 5 / 0 | |
| 0.21.0 | 5 / 0 | |
| 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 |
v0.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.