@aligent/cdk-graphql-mesh-server
A construct to host Graphql Mesh in Fargate
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/web-application-firewall.js | AI (source-diff): TypeScript-compiled CDK construct output; long lines are from bundled code, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/metrics.js | AI (source-diff): TypeScript-compiled CDK construct output; long lines are from bundled code, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/pipeline.js | AI (source-diff): TypeScript-compiled CDK construct output; long lines are from bundled code, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/redis-construct.js | AI (source-diff): TypeScript-compiled CDK construct output; long lines are from bundled code, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/fargate.js | AI (source-diff): TypeScript-compiled CDK construct output; long lines are from bundled code, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/graphql-mesh-server.js | AI (source-diff): TypeScript-compiled CDK construct output; long lines are from bundled code, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/maintenance.js | AI (source-diff): TypeScript-compiled CDK construct output; long lines are from bundled code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-sns | AI (phantom-deps): AWS SDK client loaded by convention in CDK constructs; expected pattern. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-cloudfront | AI (phantom-deps): AWS SDK client loaded by convention in CDK constructs; expected pattern. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): Runtime error-handling utility; stable pattern for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.3.7 | 4 / 9 | |
| 3.3.6 | 4 / 9 | |
| 3.3.5 | 4 / 9 | |
| 3.3.4 | 4 / 9 | |
| 3.3.3 | 4 / 9 | |
| 3.3.2 | 4 / 9 | |
| 3.3.1 | 4 / 9 | |
| 3.3.0 | 4 / 9 | |
| 3.2.1 | 4 / 9 | |
| 3.2.0 | 4 / 9 | |
| 3.1.1 | 4 / 9 | |
| 3.1.0 | 4 / 9 | |
| 3.0.0 | 4 / 9 |
v3.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
8 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
8 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.