← Home

@microsoft/fast-router

npm Repository Homepage
7
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

eisenbergeffectchrisdholtniriceawentzelmicrosoft1esfastsvcjanechu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed-stale AI (provenance): Long-standing publisher change (1893d), stable and non-malicious for this package lineage. ai
maintainer-change maintainer-added AI (maintainer-change): Historical fastsvc takeover of Microsoft fast monorepo packages, already vetted. ai
maintainer-change maintainer-removed AI (maintainer-change): Corresponds to same long-standing legitimate publisher transition. ai

Versions (showing 7 of 7)

Version Deps Published
0.4.10 1 / 38
0.4.9 1 / 38
0.4.8 1 / 38
0.2.2 1 / 38
0.2.1 1 / 38
0.2.0 1 / 38
0.1.0 1 / 38

v0.4.9

1 finding
LOW No provenance attestation provenance

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

v0.2.2

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fastsvc.

MEDIUM Publisher changed: chrisdholt → fastsvc (on 2021-05-19, unremoved on npm for 1893d) provenance

This version was published by a different npm account (fastsvc) than the most recent previously approved version (chrisdholt) on 2021-05-19. It has since remained available on npm for 1893 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.2.1

1 finding
LOW No provenance attestation provenance

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

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

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