Skip to content

Add feature product data fetch with queue#52

Open
AdamLipscore wants to merge 1 commit into
main-2.xfrom
lipscore-product-api-v2
Open

Add feature product data fetch with queue#52
AdamLipscore wants to merge 1 commit into
main-2.xfrom
lipscore-product-api-v2

Conversation

@AdamLipscore

Copy link
Copy Markdown
Contributor

No description provided.

Comment thread Model/Config.php
const XML_PATH_LIPSCORE_API_KEY = 'lipscore_general/api_key/api_key';
const XML_PATH_LIPSCORE_API_SECRET = 'lipscore_general/api_key/secret';
const XML_PATH_WEBHOOK_ENABLED = 'lipscore_general/webhook/enabled';
const XML_PATH_WEBHOOK_SECRET = 'lipscore_general/webhook/hmac_secret';

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [Bearer] <php_lang_hardcoded_secret> reported by reviewdog 🐶

Usage of hard-coded secret

Description

Storing secret values directly in the source code exposes them to unauthorized access and compromises security. This practice makes your application vulnerable to attacks.

Remediations

  • Do not hard-code secrets in your application code. Hard-coding makes sensitive information easily accessible to anyone who can view the code.
  • Do use environment variables to manage secrets securely. This method keeps sensitive information out of your codebase and makes it more difficult for unauthorized users to access.
  • Do retrieve secrets from a secure location at runtime. This approach minimizes the risk of exposing sensitive information and enhances the security of your application.
    $secret = getenv('SECRET_KEY');
  • Do consider implementing a key-management system to securely handle secrets and other sensitive information. This approach provides enhanced security measures for managing and accessing credentials.

References

@AdamLipscore AdamLipscore force-pushed the lipscore-product-api-v2 branch 2 times, most recently from 3cf4d61 to fb00daf Compare April 20, 2026 09:08
@AdamLipscore AdamLipscore force-pushed the lipscore-product-api-v2 branch from fb00daf to d21ba9d Compare April 20, 2026 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant