@opengov/ppf-backend-types
PPF Backend types
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@opengov/plc-fastify-auth-plugin | AI (dependencies): First-party OpenGov package, stable across versions. | ai | |
| dependencies | unvetted-dep:@opengov/ppf-backend-graphql-schema | AI (dependencies): First-party OpenGov package, stable across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): OpenGov org-wide npm account migration; added maintainers are org employees/service accounts, benign for this first-party package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same OpenGov org account reorganization; removed maintainers are prior org members, benign transition. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.144.0 | 2 / 6 | |
| 1.143.0 | 2 / 6 | |
| 1.142.0 | 2 / 6 | |
| 1.141.4 | 2 / 6 | |
| 1.133.2 | 2 / 6 | |
| 1.128.1 | 2 / 6 | |
| 1.113.0 | 2 / 6 | |
| 1.105.1 | 2 / 6 | |
| 1.105.0 | 2 / 6 | |
| 1.104.3 | 2 / 6 | |
| 1.104.2 | 2 / 6 | |
| 1.95.2 | 2 / 6 | |
| 1.95.1 | 2 / 6 | |
| 1.95.0 | 2 / 6 | |
| 1.3.0 | 1 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.8 | 0 / 0 | |
| 1.0.7 | 0 / 0 | |
| 1.0.6 | 0 / 0 | |
| 1.0.5 | 0 / 0 | |
| 1.0.4 | 0 / 0 | |
| 1.0.3 | 0 / 0 | |
| 1.0.2 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.144.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.133.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.128.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.113.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
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 (opengov-superadmin) than the most recent previously approved version (aailenm) on 2023-11-24, but opengov-superadmin 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.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.