← Home

@lokalise/tm-sdk

npm Repository

REST API client for the Lokalise Translation Memory service

11
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@lokalise/id-utils AI (dependencies): Same-org (@lokalise) dependency; consistent with the package's established dependency pattern. ai
provenance no-provenance AI (provenance): Lokalise org package with consistent publishing history; lack of Sigstore provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:@lokalise/id-utils AI (phantom-deps): Same-org dep; may be used transitively rather than directly imported. ai
phantom-deps phantom-dep:@lokalise/api-common AI (phantom-deps): Same-org dep; may be used transitively rather than directly imported. ai
phantom-deps phantom-dep:undici AI (phantom-deps): Known implicit runtime dependency pattern; stable for this package. ai

Versions (showing 11 of 11)

Version Deps Published
10.8.0 8 / 11
10.7.1 8 / 11
10.7.0 8 / 11
10.6.2 8 / 11
10.5.0 8 / 11
10.2.0 8 / 11
10.1.1 8 / 11
10.1.0 8 / 11
10.0.1 8 / 11
10.0.0 8 / 11
9.1.0 8 / 11

v10.8.0

1 finding
INFO No provenance attestation provenance

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

v10.7.1

1 finding
INFO No provenance attestation provenance

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

v10.7.0

1 finding
INFO No provenance attestation provenance

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

v10.6.2

1 finding
INFO No provenance attestation provenance

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

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

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

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

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

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

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

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