@epilot/automation-client MIT 32 versions

@epilot/automation-client

npm Repository Homepage

Client library for epilot automation API

32

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

daniel-bot.epilotsumanth.kanakalajulian01sdrdhanttiviljamij.pinhopraneetrosureshkumarsa.kediasebas.sauerepilot-dev-toolsalexmarqsvladcrishanwmolinarij.carneironishugoeljakub.duras.epilotjulian.maurermanikandan.subramanianberni-epilotmateus.nardogokul.kalaikovan.epilotjpcbarroskarl.epilotpriit.parnathisisernestoepilot.ernestomarta-osowieckaepilot-blomqmagabriel.epilothelyaepilotflavius_amlypen33_epilotluca-felix-epilotfriedrich_epilotbalintk-epilotankit.prasadkshitij.saxena.epiloti.agustianpaulo.henriquesniko.kozivjosh.stewart.epilotjoecaseepilotrichard.griffithsflorian.fuchs.epilotsimone.epilot

Keywords

epilotsdkautomation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@dazn/lambda-powertools-correlation-ids	AI (dependencies): Well-known DAZN Lambda powertools library; stable dependency across epilot SDK versions.	ai	2026/05/12
provenance	no-provenance	AI (provenance): Established epilot SDK package; no provenance is consistent across all 185 versions.	ai	2026/05/12
provenance	publisher-changed	AI (provenance): daniel-bot.epilot is an epilot org bot with 12 approved packages; publisher change reflects org CI/CD transition, not compromise.	ai	2026/05/06
phantom-deps	phantom-dep:stream-http	AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import.	ai	2026/04/30
phantom-deps	phantom-dep:url	AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import.	ai	2026/04/30
phantom-deps	phantom-dep:https-browserify	AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import.	ai	2026/04/30
phantom-deps	phantom-dep:util	AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import.	ai	2026/04/30
phantom-deps	phantom-dep:buffer	AI (phantom-deps): Browserify polyfill; declared for bundling, not direct import.	ai	2026/04/30

Versions (showing 32 of 32)

Version	Deps	Published
2.33.1	5 / 14	2026-04-28
2.33.0	5 / 14	2026-04-08
2.32.0	5 / 14	2026-04-01
2.31.0	5 / 14	2026-03-20
2.30.0	5 / 14	2026-03-09
2.29.0	5 / 17	2026-02-27
2.28.0	5 / 17	2026-02-12
2.27.0	5 / 17	2026-02-05
2.26.0	5 / 17	2026-01-07
2.25.0	5 / 17	2025-12-08
2.24.3	5 / 17	2025-10-28
2.24.2	5 / 17	2025-10-24
2.24.1	5 / 17	2025-08-11
2.24.0	5 / 17	2025-08-11
2.23.0	5 / 17	2025-07-29
2.22.5	5 / 17	2025-07-27
2.22.4	5 / 17	2025-07-27
2.22.3	5 / 17	2025-07-23
2.22.2	5 / 17	2025-07-23
2.22.1	5 / 17	2025-07-09
2.22.0	5 / 17	2025-07-08
2.21.0	6 / 17	2025-06-05
2.19.3	5 / 17	2025-06-25
2.19.2	5 / 17	2025-06-25
2.19.1	5 / 17	2025-06-25
2.19.0	6 / 17	2025-06-05
2.18.9	5 / 17	2025-06-19
2.18.8	5 / 17	2025-06-16
2.18.7	5 / 17	2025-06-15
2.17.3	6 / 17	2025-05-29
2.17.2	6 / 17	2025-05-19
2.17.0	6 / 17	2025-05-13

v2.33.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.32.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.31.0

2 findings

HIGH Publisher changed: aleksandr.lapushkin → anttiviljami (on 2026-03-20) provenance

This version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.30.0

2 findings

HIGH Publisher changed: aleksandr.lapushkin → daniel-bot.epilot (on 2026-03-09) provenance

This version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.24.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: anttiviljami → vladcrishan (on 2025-10-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-10-28. This could indicate a legitimate maintainer transition or an account compromise.

v2.24.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.24.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: daniel-bot.epilot → anttiviljami (on 2025-08-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-08-11. This could indicate a legitimate maintainer transition or an account compromise.

v2.24.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: daniel-bot.epilot → anttiviljami (on 2025-08-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-08-11. This could indicate a legitimate maintainer transition or an account compromise.

v2.23.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: vladcrishan → daniel-bot.epilot (on 2025-07-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-29. This could indicate a legitimate maintainer transition or an account compromise.

v2.22.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.22.4

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sebas.sauer → vladcrishan (on 2025-07-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-27. This could indicate a legitimate maintainer transition or an account compromise.

v2.22.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: daniel-bot.epilot → sebas.sauer (on 2025-07-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-23. This could indicate a legitimate maintainer transition or an account compromise.

v2.22.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: daniel-bot.epilot → sebas.sauer (on 2025-07-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-23. This could indicate a legitimate maintainer transition or an account compromise.

v2.22.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.22.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: vladcrishan → daniel-bot.epilot (on 2025-07-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-08. This could indicate a legitimate maintainer transition or an account compromise.

v2.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.19.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: josh.stewart.epilot → vladcrishan (on 2025-06-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-06-25. This could indicate a legitimate maintainer transition or an account compromise.

v2.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.18.9

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sebas.sauer → josh.stewart.epilot (on 2025-06-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-06-19. This could indicate a legitimate maintainer transition or an account compromise.

v2.18.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.17.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.