@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, 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 |
|---|---|---|---|---|
| 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 51 of 107)
| 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.86 | 12 / 10 | |
| 1.0.85 | 12 / 10 | |
| 1.0.84 | 12 / 10 | |
| 1.0.83 | 12 / 10 | |
| 1.0.82 | 12 / 10 | |
| 1.0.81 | 12 / 10 | |
| 1.0.80 | 12 / 10 | |
| 1.0.79 | 12 / 10 | |
| 1.0.78 | 12 / 10 | |
| 1.0.77 | 12 / 10 | |
| 1.0.76 | 12 / 10 | |
| 1.0.75 | 12 / 10 | |
| 1.0.74 | 12 / 10 | |
| 1.0.73 | 12 / 10 | |
| 1.0.72 | 12 / 10 | |
| 1.0.71 | 12 / 10 | |
| 1.0.70 | 12 / 10 | |
| 1.0.69 | 12 / 10 | |
| 1.0.68 | 13 / 9 | |
| 1.0.67 | 13 / 9 | |
| 1.0.66 | 13 / 9 | |
| 1.0.65 | 12 / 2 |
v1.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.81
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 (setebosu) than the most recent previously approved version (evheniihavryliuk) on 2025-04-28, but setebosu 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.
v1.0.80
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 (evheniihavryliuk) than the most recent previously approved version (setebosu) on 2025-03-19, but evheniihavryliuk 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.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
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 (setebosu) than the most recent previously approved version (andrii.cherin) on 2025-02-17, but setebosu 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.
v1.0.74
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 (setebosu) than the most recent previously approved version (andrii.cherin) on 2025-02-17, but setebosu 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.
v1.0.73
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 (andrii.cherin) than the most recent previously approved version (setebosu) on 2025-02-15, but andrii.cherin 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.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.