@epilot/app-client MIT 41 versions

@epilot/app-client

npm Repository Homepage

JavaScript client library for the epilot App API

41

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_amsergey.sedelnikov.epilotdanuta.ludwikowskalypen33_epilotajamuar_epilotluca-felix-epilots.tothfriedrich_epilotbalintk-epilotankit.prasadkshitij.saxena.epiloti.agustianpaulo.henriquesniko.kozivjosh.stewart.epilotjoecaseepilotrichard.griffithsflorian.fuchs.epilotsimone.epilot

Keywords

epilotsdkapp

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): New publisher is within the same epilot org with 37 approved packages; consistent with internal team transition.	ai	2026/05/14
dependencies	unvetted-dep:@dazn/lambda-powertools-correlation-ids	AI (dependencies): Known AWS Lambda observability library from DAZN; stable and widely used, not a security concern.	ai	2026/05/06
phantom-deps	phantom-dep:buffer	AI (phantom-deps): Browser polyfill declared for webpack bundling; not directly imported in source.	ai	2026/04/30
phantom-deps	phantom-dep:url	AI (phantom-deps): Browser polyfill declared for webpack bundling; not directly imported in source.	ai	2026/04/30
phantom-deps	phantom-dep:https-browserify	AI (phantom-deps): Browser polyfill declared for webpack bundling; not directly imported in source.	ai	2026/04/30
phantom-deps	phantom-dep:stream-http	AI (phantom-deps): Browser polyfill declared for webpack bundling; not directly imported in source.	ai	2026/04/30
phantom-deps	phantom-dep:util	AI (phantom-deps): Browser polyfill declared for webpack bundling; not directly imported in source.	ai	2026/04/30

Versions (showing 41 of 41)

Version	Deps	Published
0.13.3	7 / 9	2026-05-19
0.13.2	7 / 9	2026-05-18
0.13.1	7 / 9	2026-05-15
0.13.0	7 / 9	2026-05-07
0.12.8	7 / 9	2026-05-07
0.12.7	7 / 9	2026-05-05
0.12.6	7 / 9	2026-05-05
0.12.5	7 / 9	2026-05-04
0.12.4	7 / 9	2026-05-04
0.12.3	7 / 9	2026-04-28
0.12.2	7 / 9	2026-03-23
0.12.1	7 / 9	2026-03-17
0.10.5	7 / 12	2026-02-02
0.10.4	7 / 12	2026-01-27
0.10.3	7 / 12	2025-12-22
0.10.2	7 / 12	2025-12-16
0.10.0	7 / 12	2025-12-11
0.9.9	7 / 12	2025-11-25
0.9.7	7 / 12	2025-11-23
0.9.5	7 / 12	2025-11-19
0.9.4	7 / 12	2025-11-02
0.9.3	7 / 12	2025-11-02
0.9.2	7 / 12	2025-10-24
0.9.1	7 / 12	2025-08-28
0.9.0	7 / 12	2025-08-15
0.8.2	7 / 12	2025-08-28
0.8.1	7 / 12	2025-08-11
0.8.0	7 / 12	2025-08-11
0.7.3	7 / 12	2025-07-04
0.7.2	7 / 12	2025-07-03
0.7.1	7 / 12	2025-06-24
0.7.0	7 / 12	2025-06-19
0.6.4	7 / 12	2025-06-18
0.6.3	7 / 12	2025-06-18
0.6.2	7 / 12	2025-06-16
0.6.1	7 / 12	2025-06-16
0.6.0	7 / 12	2025-06-16
0.5.6	7 / 12	2025-06-04
0.5.5	7 / 12	2025-05-20
0.5.4	7 / 12	2025-05-07
0.5.3	7 / 12	2025-05-06

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.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: sebas.sauer → jakub.duras.epilot (on 2026-05-15) provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.8

2 findings

HIGH Publisher changed: sebas.sauer → jakub.duras.epilot (on 2026-05-07) provenance

This version was published by a different npm account than previous versions on 2026-05-07. 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.

v0.12.7

2 findings

HIGH Publisher changed: sebas.sauer → jakub.duras.epilot (on 2026-05-05) provenance

This version was published by a different npm account than previous versions on 2026-05-05. 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.

v0.12.6

2 findings

HIGH Publisher changed: sebas.sauer → jakub.duras.epilot (on 2026-05-05) provenance

This version was published by a different npm account than previous versions on 2026-05-05. 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.

v0.12.5

2 findings

HIGH Publisher changed: sebas.sauer → jakub.duras.epilot (on 2026-05-04) provenance

This version was published by a different npm account than previous versions on 2026-05-04. 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.

v0.12.4

2 findings

HIGH Publisher changed: sebas.sauer → jakub.duras.epilot (on 2026-05-04) provenance

This version was published by a different npm account than previous versions on 2026-05-04. 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.

v0.12.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.

v0.12.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.

v0.12.1

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.

v0.10.5

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.

v0.10.4

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.

v0.10.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.

v0.10.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.

v0.10.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.

v0.9.9

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.

v0.9.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.

v0.9.5

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.

v0.9.4

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.

v0.9.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.

v0.9.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.

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

2 findings

HIGH Publisher changed: sebas.sauer → anttiviljami (on 2025-08-15) provenance

This version was published by a different npm account than previous versions on 2025-08-15. 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.

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

2 findings

HIGH Publisher changed: sebas.sauer → anttiviljami (on 2025-08-11) provenance

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.

LOW No provenance attestation provenance

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

v0.8.0

2 findings

HIGH Publisher changed: sebas.sauer → anttiviljami (on 2025-08-11) provenance

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.

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

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.

v0.5.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.