← Home

@yarn-tool/tag

npm Repository Homepage

git tag a package

10
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bluelovers

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @yarn-tool/tag; levenshtein match against 'pg' is coincidental, no impersonation intent. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic import resolves package.json via path join — standard workspace tooling pattern, not arbitrary module loading. ai
phantom-deps phantom-dep:pkg-dir AI (phantom-deps): Phantom-dep heuristic false positive; pkg-dir is a transitive/config-referenced dep in this workspace tool. ai
phantom-deps phantom-dep:path-dir-normalize AI (phantom-deps): Same publisher's package; phantom-dep heuristic fires on config references, not a real risk. ai

Versions (showing 10 of 10)

Version Deps Published
3.0.12 9 / 0
3.0.11 9 / 0
3.0.9 9 / 0
3.0.6 9 / 0
3.0.5 9 / 0
3.0.4 10 / 0
3.0.3 10 / 0
3.0.2 10 / 0
3.0.1 10 / 0
3.0.0 10 / 0

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.