@v-c/resize-observer
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 org package (@v-c/*); missing metadata is consistent across the ecosystem, not a spam indicator. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.1.3 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.1.1 | 2 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.8 | 2 / 0 | |
| 1.0.7 | 2 / 0 | |
| 1.0.6 | 2 / 0 | |
| 1.0.5 | 2 / 0 | |
| 1.0.4 | 2 / 0 | |
| 1.0.3 | 2 / 0 | |
| 1.0.1 | 2 / 0 | |
| 1.0.0 | 2 / 0 | |
| 0.0.4 | 2 / 0 | |
| 0.0.3 | 2 / 0 |
v1.1.3
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.