@fastify/secure-session
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Known maintainer roster churn within official fastify org, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Stable, low-frequency official package; dormancy is expected. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Diff vs v8.1.0 shows only lint script changes; no injected content. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Static default salt constant for key derivation, documented in source; not a malicious payload pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 8.3.0 | 3 / 8 | |
| 8.2.0 | 3 / 9 | |
| 8.1.1 | 3 / 9 | |
| 8.1.0 | 3 / 8 | |
| 8.0.0 | 3 / 8 |
v8.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matteo.collina) than the most recent previously approved version (eomm) on 2025-04-12, but matteo.collina 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.
v8.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (fdawgs) than the most recent previously approved version (matteo.collina) on 2025-01-11, but fdawgs 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.
v8.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (eomm) than the most recent previously approved version (matteo.collina) on 2024-09-21, 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.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.