@epilot/notes-client MIT 42 versions

@epilot/notes-client

npm Repository Homepage

JavaScript client library for Epilot's Notes API

42

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

daniel-bot.epilotsumanth.kanakalajulian01sdrdhanttiviljamij.pinhopraneetrosureshkumarsa.kediasebas.sauerepilot-dev-toolsalexmarqsvladcrishanwmolinarij.carneironishugoeljakub.duras.epilotjulian.maurermanikandan.subramanianberni-epilotmateus.nardogokul.kalaikovan.epilotkarl.epilotpriit.parnathisisernestoepilot.ernestomarta-osowieckaepilot-blomqmagabriel.epilothelyaepilotflavius_amsergey.sedelnikov.epilotdanuta.ludwikowskaajamuar_epilotluca-felix-epilots.tothmarta.pestkafriedrich_epilotbalintk-epilotankit.prasadirockelkshitij.saxena.epilotpaulo.henriquesniko.kozivjosh.stewart.epilotjoecaseepilotrichard.griffithsflorian.fuchs.epilotsimone.epilot

Keywords

epilotsdkentity

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): Known AWS Lambda observability library from DAZN; stable, widely used, not a risk for this package.	ai	2026/05/06
phantom-deps	phantom-dep:url	AI (phantom-deps): Browser polyfill declared for webpack bundling; stable pattern for this SDK client.	ai	2026/04/30
phantom-deps	phantom-dep:util	AI (phantom-deps): Browser polyfill declared for webpack bundling; stable pattern for this SDK client.	ai	2026/04/30
phantom-deps	phantom-dep:buffer	AI (phantom-deps): Browser polyfill declared for webpack bundling; stable pattern for this SDK client.	ai	2026/04/30
phantom-deps	phantom-dep:stream-http	AI (phantom-deps): Browser polyfill declared for webpack bundling; stable pattern for this SDK client.	ai	2026/04/30
phantom-deps	phantom-dep:https-browserify	AI (phantom-deps): Browser polyfill declared for webpack bundling; stable pattern for this SDK client.	ai	2026/04/30

Versions (showing 42 of 42)

Version	Deps	Published
0.23.1	7 / 9	2026-06-17
0.22.0	7 / 9	2026-04-28
0.21.7	7 / 12	2026-02-13
0.21.5	7 / 12	2025-09-10
0.21.4	7 / 12	2025-09-10
0.21.3	7 / 12	2025-08-26
0.19.3	7 / 12	2025-05-16
0.19.2	7 / 12	2025-05-16
0.19.1	7 / 12	2025-05-16
0.19.0	7 / 12	2025-02-18
0.18.0	7 / 12	2025-01-31
0.17.1	7 / 12	2025-01-29
0.17.0	7 / 12	2025-01-17
0.16.0	7 / 12	2024-10-11
0.15.0	7 / 12	2024-10-11
0.14.0	7 / 12	2024-10-10
0.13.0	7 / 12	2024-10-07
0.12.0	7 / 12	2024-10-04
0.11.0	7 / 12	2024-10-04
0.10.1	7 / 12	2024-10-01
0.10.0	7 / 12	2024-09-25
0.9.1	7 / 12	2024-09-24
0.9.0	7 / 12	2024-09-24
0.8.0	7 / 12	2024-09-24
0.7.0	7 / 12	2024-09-20
0.6.3	7 / 12	2024-09-19
0.6.2	7 / 12	2024-09-18
0.6.1	7 / 12	2024-09-18
0.6.0	7 / 12	2024-09-18
0.5.5	7 / 12	2024-09-17
0.5.4	7 / 12	2024-09-16
0.5.3	7 / 12	2024-09-16
0.5.2	7 / 12	2024-09-16
0.5.1	7 / 12	2024-09-16
0.5.0	7 / 12	2024-09-16
0.4.1	7 / 12	2024-09-13
0.4.0	7 / 12	2024-09-13
0.3.2	7 / 12	2024-09-12
0.3.1	7 / 12	2024-09-12
0.3.0	7 / 12	2024-09-11
0.2.0	7 / 13	2024-09-09
0.1.0	7 / 13	2024-09-07

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.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: anttiviljami → epilot.ernesto (on 2025-01-31, known maintainer) provenance

This version was published by a different npm account (epilot.ernesto) than the most recent previously approved version (anttiviljami) on 2025-01-31, but epilot.ernesto is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.17.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: epilot.ernesto → anttiviljami (on 2025-01-29, known maintainer) provenance

This version was published by a different npm account (anttiviljami) than the most recent previously approved version (epilot.ernesto) on 2025-01-29, but anttiviljami is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

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.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.8.0

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.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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.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: anttiviljami → epilot.ernesto (on 2024-09-12, known maintainer) provenance

This version was published by a different npm account (epilot.ernesto) than the most recent previously approved version (anttiviljami) on 2024-09-12, but epilot.ernesto is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.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: epilot.ernesto → anttiviljami (on 2024-09-11, known maintainer) provenance

This version was published by a different npm account (anttiviljami) than the most recent previously approved version (epilot.ernesto) on 2024-09-11, but anttiviljami is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.0

1 finding

LOW No provenance attestation provenance

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

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