This website uses cookies to ensure you get the best experience.
Learn more.
A public repository caches a directory containing a private registry credential alongside downloaded dependencies. The team believes a hard-to-guess cache key prevents exposure. What is the correct assessment?
Published
- An obscure cache key provides the same confidentiality guarantee as a repository secret.
- Moving the credential into a cached hidden file makes it safe.
- Cache retention automatically revokes every credential stored in the cache.
- Exclude credentials from caches and supply them as secrets.
Comments — 0
Sign in to comment