@studyportals/fawkes
A package to centralize SEO related logic for SBLP and Sitemap Generator.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Package uses named exports only; empty dist/index.js is intentional. Missing repo/keywords are cosmetic for an internal org package. | ai | |
| phantom-deps | phantom-dep:@studyportals/ranking-api-interface | AI (phantom-deps): Same org scope; likely used via re-exports or type-only imports not caught by the heuristic. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 8.7.2 | 4 / 13 | |
| 8.7.1 | 4 / 13 | |
| 8.7.0 | 4 / 13 | |
| 8.6.1 | 4 / 13 | |
| 8.6.0 | 4 / 13 | |
| 8.5.2 | 4 / 13 | |
| 8.5.1 | 4 / 13 | |
| 8.5.0 | 4 / 13 | |
| 8.4.0 | 4 / 13 | |
| 8.3.0 | 4 / 13 | |
| 8.2.3 | 4 / 13 | |
| 8.2.2 | 4 / 13 | |
| 8.2.1 | 4 / 13 | |
| 8.2.0 | 4 / 13 | |
| 8.1.1 | 4 / 13 | |
| 8.0.1 | 4 / 13 |
v8.7.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 (stormyy) than the most recent previously approved version (orlandoliccardo) on 2026-05-14, but stormyy 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.
v8.7.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 (orlandoliccardo) than the most recent previously approved version (giampiero_sp) on 2026-04-29, but orlandoliccardo 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.
v8.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.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 (stormyy) than the most recent previously approved version (alparslanylmaz) on 2026-02-17, but stormyy 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.
v8.6.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 (stormyy) than the most recent previously approved version (muratcolyaran1) on 2026-02-05, but stormyy 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.
v8.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.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 (orlandoliccardo) than the most recent previously approved version (muratcolyaran1) on 2025-10-02, but orlandoliccardo 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.
v8.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 (alparslanylmaz) than the most recent previously approved version (muratcolyaran1) on 2025-10-01, but alparslanylmaz 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.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.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 (alparslanylmaz) than the most recent previously approved version (muratcolyaran1) on 2025-09-29, but alparslanylmaz 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.
v8.2.3
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 (orlandoliccardo) than the most recent previously approved version (muratcolyaran1) on 2025-09-16, but orlandoliccardo 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.
v8.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 (muratcolyaran1) than the most recent previously approved version (stormyy) on 2025-09-15, but muratcolyaran1 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.
v8.2.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 (muratcolyaran1) than the most recent previously approved version (stormyy) on 2025-09-11, but muratcolyaran1 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.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.