@v-c/notification
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped Vue component library in @v-c/* namespace; sparse metadata is consistent with internal/monorepo tooling pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with the @v-c/* package family style; not a malware indicator here. | ai |
v2.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aibayanyu) than the most recent previously approved version (selicens) on 2026-07-02, but aibayanyu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.