← Home

@fluent/syntax

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

Maintainers

eemelizbranieckitatumcreativeflod

Keywords

localizationl10ninternationalizationi18nftlpluralgenderlocalelanguageformattingtranslatetranslationformatastserializerparser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed-stale AI (provenance): Publisher change is from 2021, long-stable, not indicative of takeover. ai
npm-metadata url-dep:@fluent/dedent AI (npm-metadata): file: devDependency is a normal monorepo-local reference. ai

Versions (showing 8 of 8)

Version Deps Published
0.19.0 0 / 1
0.18.1 0 / 1
0.18.0 0 / 1
0.17.0 0 / 1
0.16.1 0 / 1
0.16.0 0 / 1
0.15.0 0 / 1
0.14.0 0 / 1

v0.18.1

2 findings
MEDIUM Publisher changed: mozpike → eemeli (on 2022-05-03, unremoved on npm for 1540d) provenance

This version was published by a different npm account (eemeli) than the most recent previously approved version (mozpike) on 2022-05-03. It has since remained available on npm for 1540 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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
MEDIUM Publisher changed: mozpike → eemeli (on 2021-09-13, unremoved on npm for 1772d) provenance

This version was published by a different npm account (eemeli) than the most recent previously approved version (mozpike) on 2021-09-13. It has since remained available on npm for 1772 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.17.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: stasm → mozpike (on 2021-04-09, known maintainer) provenance

This version was published by a different npm account (mozpike) than the most recent previously approved version (stasm) on 2021-04-09, but mozpike 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.16.1

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. Only ~12% of npm packages have provenance, so this is common but not ideal.