builder icon indicating copy to clipboard operation
builder copied to clipboard

Fix: SDKs Eval

Open samijaber opened this issue 1 year ago • 3 comments

Description

samijaber avatar Oct 11 '24 15:10 samijaber

🦋 Changeset detected

Latest commit: b45d60e59b964ec1cdcaf33504a1f0bdb71a02d8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages
Name Type
@builder.io/sdk-angular Patch
@builder.io/sdk-react-nextjs Patch
@builder.io/sdk-qwik Patch
@builder.io/sdk-react Patch
@builder.io/sdk-react-native Patch
@builder.io/sdk-solid Patch
@builder.io/sdk-svelte Patch
@builder.io/sdk-vue Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

changeset-bot[bot] avatar Oct 11 '24 15:10 changeset-bot[bot]

⚠️ GitGuardian has uncovered 8 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard. Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
11707119 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/sdks/snippets/angular/src/app/product-details/product-details.component.ts View secret
11707119 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/sdks/snippets/angular-ssr/src/app/nav-bar/nav-bar.resolver.ts View secret
11707119 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/sdks/snippets/angular-ssr/src/app/product-editorial/product-editorial.resolver.ts View secret
11707119 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/sdks/snippets/angular-ssr/src/app/product-details/product-details.resolver.ts View secret
11707119 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/sdks/snippets/angular/src/app/nav-bar/nav-bar.component.ts View secret
14200383 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/core/src/builder.class.test.ts View secret
14200384 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/core/src/builder.class.test.ts View secret
14200385 Triggered Generic High Entropy Secret 10d70402f5501a7eef763baee710954c52f7a7c6 packages/core/src/builder.class.test.ts View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

gitguardian[bot] avatar Oct 18 '24 23:10 gitguardian[bot]

does this also handle the fact that the bindings rarely actually look like state.foo and instead look like var _virtual_index=state.foo;return _virtual_index

looking at your PR it seems to assume the binding value is always in the unprocessed format (but could be wrong)

tl;dr in the app we compile TS to JS, and the way our rollup setup works state.whatever in JS becomes var _virtual_index=state.whatever;return _virtual_index so we'd ideally be able to match that and parse from there as well

steve8708 avatar Oct 21 '24 17:10 steve8708