Skip to content

[NEW CONTENT] Document best practices for consuming community packages #332

@zastrowm

Description

@zastrowm

Proposed Content

Document general purpose best practices when consuming community packages:

  • Pin to patch versions
  • Vet by reading the source code
  • Look for minimal dependencies

Location

Under community packages

Rationale

Want to guide folks to the latest best practices/supply-chain problems

Content Outline (Optional)

No response

References

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions