@lokalise/expert-api-s2s-client-mocks
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.
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:zod | AI (phantom-deps): Declared as runtime dep but used via config/type references; stable pattern for this org's packages. | ai | |
| phantom-deps | phantom-dep:@lokalise/fastify-extras | AI (phantom-deps): Same-org dep used in config/type context; not a direct import concern for this mock utility package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is same-org @lokalise scoped package; consistent with this package's dependency pattern. | ai | |
| phantom-deps | phantom-dep:@lokalise/backend-http-client | AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires on indirect usage patterns common in this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Lokalise mock library; sparse README is expected for org-internal tooling, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@lokalise/node-api | AI (phantom-deps): Same-org dependency; phantom-dep heuristic fires on indirect usage patterns common in this package family. | ai | |
| phantom-deps | phantom-dep:openid-client | AI (phantom-deps): Referenced in config files; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.6.1 | 5 / 10 | |
| 1.6.0 | 5 / 10 | |
| 1.5.0 | 5 / 10 | |
| 1.4.0 | 4 / 10 | |
| 1.3.0 | 4 / 10 | |
| 1.2.2 | 4 / 10 | |
| 1.2.1 | 6 / 10 | |
| 1.2.0 | 6 / 9 | |
| 1.1.1 | 6 / 9 | |
| 1.1.0 | 6 / 9 | |
| 1.0.2 | 6 / 9 | |
| 1.0.1 | 6 / 9 |
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.