@opengis/fastify-auth
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): fastify is a declared runtime dependency used via config/plugin pattern; stable false positive for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): env enumeration is inside a debug trace block gated on config.trace; not exfiltration. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.1.24 | 9 / 5 | |
| 1.1.23 | 9 / 5 | |
| 1.1.22 | 9 / 5 | |
| 1.1.21 | 9 / 5 | |
| 1.1.20 | 9 / 5 | |
| 1.1.19 | 9 / 5 | |
| 1.1.18 | 9 / 5 | |
| 1.1.17 | 9 / 5 | |
| 1.1.15 | 9 / 4 | |
| 1.1.14 | 9 / 3 | |
| 1.1.13 | 10 / 2 | |
| 1.1.12 | 10 / 2 | |
| 1.1.11 | 10 / 2 | |
| 1.1.10 | 10 / 2 | |
| 1.1.9 | 10 / 2 | |
| 1.1.8 | 10 / 2 | |
| 1.1.7 | 10 / 2 | |
| 1.1.3 | 10 / 2 | |
| 1.1.2 | 10 / 2 | |
| 1.1.1 | 12 / 2 | |
| 1.1.0 | 12 / 2 | |
| 1.0.94 | 12 / 2 | |
| 1.0.93 | 12 / 2 | |
| 1.0.92 | 12 / 10 | |
| 1.0.91 | 12 / 10 | |
| 1.0.90 | 12 / 10 | |
| 1.0.89 | 12 / 10 | |
| 1.0.88 | 12 / 10 | |
| 1.0.87 | 12 / 10 | |
| 1.0.85 | 12 / 10 |
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.