← Home

@financial-times/dotcom-server-navigation

npm Homepage

This package provides tools to fetch and format navigation data for FT.com.

10
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

the-ftrowanmanningcheealexwilsonaendraemmalewisnotleeseraph2000hamza.samihrobertboultonrobgodfrey

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Long-lived FT org package with 206 versions; dormancy followed by internal dep migration is consistent with org maintenance cadence. ai
publish-pattern new-deps-added AI (publish-pattern): @dotcom-reliability-kit/errors is an FT internal package replacing http-errors; low supply-chain risk. ai
phantom-deps phantom-dep:@types/deep-freeze AI (phantom-deps): Type-only package; not directly imported by convention, stable false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
13.10.0 6 / 2
13.8.0 6 / 2
13.7.0 6 / 2
13.6.1 6 / 2
13.6.0 6 / 2
13.4.0 6 / 2
13.3.0 6 / 2
13.2.3 6 / 2
13.2.0 6 / 2
13.0.0 6 / 2

v13.8.0

1 finding
LOW No provenance attestation provenance

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

v13.7.0

1 finding
LOW No provenance attestation provenance

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

v13.6.1

1 finding
LOW No provenance attestation provenance

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

v13.6.0

1 finding
LOW No provenance attestation provenance

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

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

v13.3.0

1 finding
LOW No provenance attestation provenance

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

v13.2.3

1 finding
LOW No provenance attestation provenance

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

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

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