serve-favicon MIT 22 versions

serve-favicon

npm Repository Homepage

favicon serving middleware with caching

22

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

dougwilsonulisesgascon

Keywords

expressfaviconmiddleware

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): ulisesgascon is a known Express.js TC member; this is part of the documented expressjs org maintainer transition.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): ulisesgascon is a recognized Express.js maintainer with extensive npm track record (651 approved versions).	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy ended by legitimate Express.js org maintainer transition; ulisesgascon is updating many expressjs/* packages.	ai	2026/04/23

Versions (showing 22 of 22)

Version	Deps	Published
2.5.1	5 / 11	2025-06-10
2.5.0	5 / 11	2018-03-29
2.4.5	5 / 11	2017-09-26
2.4.4	5 / 11	2017-09-12
2.4.3	5 / 11	2017-05-16
2.4.2	4 / 8	2017-03-25
2.4.1	4 / 8	2017-02-28
2.4.0	4 / 8	2017-02-20
2.3.2	4 / 4	2016-11-17
2.3.0	4 / 4	2015-06-14
2.2.1	4 / 4	2015-05-14
2.2.0	4 / 4	2014-12-19
2.1.7	3 / 4	2014-11-20
2.1.6	3 / 5	2014-10-17
2.1.5	3 / 5	2014-09-24
2.1.4	3 / 5	2014-09-15
2.1.3	3 / 5	2014-09-08
2.1.2	3 / 5	2014-09-06
2.1.1	3 / 5	2014-08-25
2.1.0	2 / 6	2014-08-25
2.0.1	1 / 5	2014-06-05
2.0.0	1 / 4	2014-05-02

v2.5.1

2 findings

HIGH Publisher changed: dougwilson → ulisesgascon (on 2025-06-10) provenance

This version was published by a different npm account than previous versions on 2025-06-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.5

1 finding

LOW No provenance attestation provenance

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

v2.4.4

1 finding

LOW No provenance attestation provenance

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

v2.4.3

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.7

1 finding

LOW No provenance attestation provenance

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

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

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