@fastify/swagger
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): The base64 string in the test file is a PNG image fixture (iVBORw0KGgo... is the standard PNG header). It's in a TypeScript type test file, not production code, and poses no security risk. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 9.8.1 | 5 / 12 | |
| 9.8.0 | 5 / 12 | |
| 9.7.0 | 5 / 12 | |
| 9.6.1 | 5 / 12 | |
| 9.6.0 | 5 / 12 | |
| 9.5.2 | 5 / 12 | |
| 9.5.1 | 5 / 13 | |
| 9.5.0 | 5 / 13 | |
| 9.4.2 | 5 / 13 | |
| 9.4.1 | 5 / 13 | |
| 9.4.0 | 5 / 12 | |
| 9.3.0 | 5 / 12 | |
| 9.2.0 | 5 / 12 | |
| 9.1.0 | 5 / 12 | |
| 9.0.1 | 5 / 12 | |
| 9.0.0 | 5 / 12 |
v9.8.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 (climba03003) than the most recent previously approved version (eomm) on 2026-07-13, 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.
v9.8.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 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.
v9.5.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 (kibertoad) than the most recent previously approved version (fdawgs) on 2025-04-13, but kibertoad 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.
v9.4.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 (fdawgs) on 2025-01-19, 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.
v9.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.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 (fdawgs) than the most recent previously approved version (matteo.collina) on 2024-11-22, 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.
v9.3.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 (gurgunday) on 2024-11-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.
v9.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 (gurgunday) than the most recent previously approved version (matteo.collina) on 2024-10-12, but gurgunday 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.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.