@lokalise/expert-api-s2s-client No license 25 versions

@lokalise/expert-api-s2s-client

npm Repository Homepage

FIXME: describe why it is here, not a separate repo, not a Harmony package, not combined with packages/backend-plugins/populate-expert-user/clients/BackendExpertHttpClient, not combined with Lokalise Node.js API client

25

Versions

—

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

bodrovismarcocardosolokbotlokalisekibertoadcarlos_gameroaplokalisefilippos.mikropoulosandrew_lokalisedariacmmattfinucanebezlydmitrycasamitjanabartoszdrozd-lokalisejhfedzerikapalillontrpilot-lokalise

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@lokalise/fastify-extras	AI (dependencies): Same-org Lokalise dependency consistent with this package's ecosystem; stable pattern across versions.	ai	2026/05/24
phantom-deps	phantom-dep:zod	AI (phantom-deps): zod is a declared runtime dep; phantom-dep false positive for this package.	ai	2026/05/23
dependencies	unvetted-dep:@lokalise/workspaces-api-schemas	AI (dependencies): Internal @lokalise org package; same publisher ecosystem, stable false positive.	ai	2026/05/08
dependencies	unvetted-dep:@lokalise/common-api-schemas	AI (dependencies): Internal @lokalise org package; same publisher ecosystem, stable false positive.	ai	2026/05/08
dependencies	unvetted-dep:@lokalise/id-utils	AI (dependencies): Internal @lokalise org package; same publisher ecosystem, stable false positive.	ai	2026/05/08
phantom-deps	phantom-dep:@lokalise/backend-http-client	AI (phantom-deps): Same-org dep declared but not directly imported; stable false positive for this package.	ai	2026/05/04
bogus-package	bogus-package	AI (bogus-package): Internal @lokalise org package; thin README is expected for internal tooling, not a spam indicator.	ai	2026/05/04

Versions (showing 25 of 25)

Version	Deps	Published
1.17.2	7 / 9	2026-05-01
1.17.1	7 / 9	2026-05-01
1.17.0	7 / 9	2026-04-30
1.16.0	7 / 9	2026-03-30
1.15.0	7 / 9	2026-03-27
1.14.0	7 / 9	2026-03-25
1.13.0	7 / 9	2026-03-09
1.12.0	7 / 9	2026-03-09
1.11.0	7 / 9	2026-03-04
1.10.0	7 / 9	2026-02-09
1.8.2	7 / 9	2025-11-25
1.8.1	7 / 9	2025-10-27
1.8.0	7 / 9	2025-10-24
1.7.7	7 / 9	2025-10-14
1.7.4	9 / 8	2025-10-08
1.7.0	9 / 8	2025-09-30
1.5.0	9 / 8	2025-09-19
1.4.1	9 / 8	2025-09-18
1.4.0	9 / 8	2025-09-16
1.3.2	9 / 8	2025-09-05
1.3.0	9 / 8	2025-09-02
1.2.1	9 / 8	2025-09-02
1.1.0	8 / 8	2025-09-01
1.0.2	8 / 8	2025-08-28
1.0.1	8 / 8	2025-08-26

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

v1.17.1

1 finding

LOW No provenance attestation provenance

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

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

v1.16.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.

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.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.

v1.13.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.

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

v1.11.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.

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

v1.8.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.

v1.8.1

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

v1.4.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.

v1.4.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.

v1.3.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.

v1.3.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.

v1.2.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.

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

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