@fastify/swagger-ui
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Handoff to fastify contributor fdawgs; legitimate maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fdawgs is a listed contributor on official fastify org package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 content in examples/theme.js is a PNG favicon image (iVBORw0KGgo prefix). Embedding small images as Base64 is a standard, benign pattern. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP 127.0.0.1 in playwright.config.js is localhost used for E2E test configuration — standard and benign. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is in the bundled swagger-ui-standalone-preset.js (webpack bundle from swagger-ui-dist). This is standard webpack module definition boilerplate, not malicious code. | ai | |
| dependencies | unvetted-dep:@fastify/static | AI (dependencies): @fastify/static is the official Fastify static file plugin, a core ecosystem package. Its use here is appropriate and expected. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 6.1.0 | 5 / 15 | |
| 6.0.0 | 5 / 15 | |
| 5.2.6 | 5 / 15 | |
| 5.2.5 | 5 / 15 | |
| 5.2.4 | 5 / 15 | |
| 5.2.3 | 5 / 16 | |
| 5.2.2 | 5 / 16 | |
| 5.2.1 | 5 / 16 | |
| 5.2.0 | 5 / 15 | |
| 5.1.0 | 5 / 15 | |
| 5.0.1 | 5 / 15 | |
| 5.0.0 | 5 / 15 |
v6.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 (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.
v5.2.2
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 2025-02-16, 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.
v5.2.1
2 findingsThis version was published by a different npm account than previous versions on 2025-01-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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 (matteo.collina) than the most recent previously approved version (eomm) on 2024-10-15, 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.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.