@platformatic/graphql-composer
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Platformatic migrated to GitHub Actions CI publishing with SLSA attestation; this is a legitimate org-level automation change. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Rapid publish is consistent with automated CI/CD pipeline; SLSA attestation confirms legitimate origin. | ai | |
| phantom-deps | phantom-dep:pino | AI (phantom-deps): pino is a declared dep used via config/indirect usage; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:abstract-logger | AI (phantom-deps): abstract-logger is a declared dep used via config/indirect usage; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 7 / 5 | |
| 0.10.1 | 7 / 4 | |
| 0.10.0 | 7 / 4 | |
| 0.9.0 | 7 / 4 | |
| 0.8.2 | 7 / 4 | |
| 0.8.1 | 7 / 4 | |
| 0.8.0 | 7 / 4 | |
| 0.7.3 | 7 / 4 | |
| 0.7.2 | 7 / 4 | |
| 0.7.1 | 7 / 4 |
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.