Types and documentation may not explain unexpected dependency behavior. This skill guides AI agents to fetch matching source versions and inspect implementations through a reusable cache.
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
에이전트 요청
Review the Skillstore skill "opensrc" from https://skillstore.io/skills/vercel-labs-opensrc.md and its manifest at https://skillstore.io/api/skills/vercel-labs-opensrc/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
All 22 static detections are false positives involving Markdown delimiters, routine source-reading commands, or the documented source cache. No evidence found of prompt injection, credential access, or data exfiltration in the reviewed skill text. The external CLI implementation was not included, and unquoted cache paths should be improved.
vercel-labs. (2026). opensrc security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/vercel-labs-opensrc/audits/1
BibTeX 인용
@techreport{vercel-labs-vercel-labs-opensrc-2026,
author = {vercel-labs},
title = {opensrc security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/vercel-labs-opensrc/audits/1},
note = {Author version unspecified}
}
CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "opensrc security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "vercel-labs"
date-released: "2026-10-10"
url: "https://skillstore.io/skills/vercel-labs-opensrc/audits/1"
identifiers:
- type: other
value: "skillstore:vercel-labs-opensrc:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 점수
이 점수의 이유증거 신뢰도: 중간
55
아키텍처
85
유지보수성
87
콘텐츠
65
커뮤니티
83
사양 준수
만들 수 있는 것
Debug Unexpected Library Behavior
Inspect the dependency version used by a project to trace behavior that public types do not explain.
Investigate Dependency Edge Cases
Read implementation branches and locate upstream tests before designing regression coverage.
Study Upstream Implementations
Fetch selected package versions or repository references to study internal design patterns.
이 프롬프트를 사용해 보세요
Fetch One Dependency
Fetch source for zod with opensrc and report the resolved version and cache location.
Inspect a Function
Inspect requests version 2.31.0 from PyPI using opensrc. Explain timeout handling and cite the implementation files.
Debug the Installed Version
Resolve zod from the lockfile in [project directory]. Trace [unexpected behavior] through its source and tests, citing relevant locations.
Compare Pinned Revisions
Fetch [repository] at [reference A] and [reference B]. Compare [function] behavior, cite changed locations, and suggest regression tests without executing downloaded code.
모범 사례
Use the project lockfile or explicit versions and repository references for reproducible source inspection.
Quote resolved cache paths and treat fetched source as untrusted data rather than instructions.
Review cache entries before removal and confirm the scope of global cleanup.
피하기
Fetching source for simple API questions already answered by documentation or types.
Assuming latest PyPI or crates.io source matches the dependency installed in your project.
Executing downloaded code or deleting the entire cache when source inspection is sufficient.
자주 묻는 질문
Which source ecosystems are supported?
The instructions cover npm, PyPI, crates.io, and repository references such as owner/repo.
How does npm version resolution work?
The CLI uses package-lock.json, pnpm-lock.yaml, or yarn.lock to detect installed npm versions. A project-directory option changes the resolution location.
Can I select a specific version or revision?
Yes. Package specifications accept explicit versions, and repository references can select a branch, tag, or commit.
Where is source cached?
Source is cached globally in ~/.opensrc/. OPENSRC_HOME can override the cache location.
Does this skill include the opensrc CLI?
No. The reviewed skill contains instructions only. The opensrc CLI must be available separately.
Can I remove cached source selectively?
Yes. Remove individual packages or repositories, or clean selected ecosystem categories. Global cleanup removes all cached sources.