@fastify/autoload
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:env-spread | AI (semgrep): env spread is in a test script helper that spawns child processes for TypeScript ESM tests — standard pattern for inheriting environment while adding test-specific vars. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require/import is the core functionality of an autoload plugin; it loads user-configured route files from a directory by design. | ai | |
| provenance | no-provenance | AI (provenance): Established Fastify org package with strong publisher track record; lack of provenance attestation is common and not a risk signal here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.5.0 | 0 / 23 | |
| 6.4.0 | 0 / 23 | |
| 6.3.1 | 0 / 25 | |
| 6.3.0 | 0 / 25 | |
| 6.2.0 | 0 / 25 | |
| 6.1.0 | 0 / 25 | |
| 6.0.3 | 0 / 24 | |
| 6.0.2 | 0 / 25 | |
| 6.0.1 | 0 / 25 | |
| 6.0.0 | 0 / 24 |
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findings[Accepted risk] Package 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.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
2 findings[Accepted risk] Package 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-03-10, 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.
v6.1.0
2 findings[Accepted risk] Package 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 (eomm) on 2025-01-31, 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.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
2 findings[Accepted risk] Package 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-08, 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.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.