@fastify/passport
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-added | AI (maintainer-change): Publisher is a known maintainer within the fastify org, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal org maintainer rotation for fastify scoped packages. | ai | |
| phantom-deps | phantom-dep:fastify-plugin | AI (phantom-deps): Used in TS source, likely missed by import heuristic; standard fastify plugin dep. | ai | |
| phantom-deps | phantom-dep:@fastify/flash | AI (phantom-deps): Same-org dep used indirectly; not a supply-chain concern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Consistent with slow-moving, mature official plugin release cadence. | ai | |
| dependencies | unvetted-dep:@fastify/flash | AI (dependencies): @fastify/flash is a first-party Fastify organization package; stable dependency for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 2 / 22 | |
| 3.0.2 | 2 / 20 | |
| 3.0.1 | 2 / 24 | |
| 3.0.0 | 2 / 24 |
v4.0.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 (fdawgs) on 2026-07-26, 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.
v3.0.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 (eomm) than the most recent previously approved version (matteo.collina) on 2024-09-22, 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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.