graphql-elasticsearch-transformer
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:graphql-transformer-common | AI (dependencies): graphql-transformer-common is a sibling package in the aws-amplify/amplify-category-api monorepo; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): AWS Amplify monorepo package; provenance not attested but publisher is well-established with strong track record. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.2.90 | 5 / 3 | |
| 5.2.89 | 5 / 3 | |
| 5.2.88 | 5 / 3 | |
| 5.2.87 | 5 / 3 | |
| 5.2.86 | 5 / 3 | |
| 5.2.85 | 5 / 3 | |
| 5.2.84 | 5 / 3 | |
| 5.2.83 | 5 / 3 | |
| 5.2.82 | 5 / 3 | |
| 5.2.81 | 5 / 3 | |
| 5.2.80 | 5 / 3 | |
| 5.2.79 | 5 / 3 |
v5.2.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.