← Home

@fastify/cookie

npm Repository Homepage

Plugin for fastify to add support for cookies

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

Maintainers

simonebdelvedormatteo.collinajsumnerszektheommfox1tairhornskibertoadclimba03003galvezsimenbgurgundaytony133metcoder95jean-micheletilteooodfdawgs

Keywords

fastifycookie

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Normal fastify org maintainer rotation, publisher is a known prior maintainer. ai
maintainer-change maintainer-removed AI (maintainer-change): Org maintainer rotation, not a takeover indicator here. ai
publish-pattern dormant-publish AI (publish-pattern): Established, high-trust package resuming normal maintenance cadence. ai

Versions (showing 6 of 6)

Version Deps Published
11.1.2 2 / 8
11.1.1 2 / 8
11.1.0 2 / 8
11.0.2 2 / 9
11.0.1 2 / 9
11.0.0 3 / 9

v11.1.2

1 finding
LOW No provenance attestation provenance

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

v11.1.1

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: eomm → climba03003 (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (climba03003) than the most recent previously approved version (eomm) on 2026-07-09, but climba03003 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.

v11.1.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: fdawgs → eomm (on 2026-07-08, known maintainer) provenance

This version was published by a different npm account (eomm) than the most recent previously approved version (fdawgs) on 2026-07-08, but eomm 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.

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

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