@primevue/forms
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): Official PrimeTek monorepo sub-package; sparse metadata is normal for this publishing pattern. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package lacks description but is legitimate and well-known. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @primevue/forms name, unrelated to cors; false positive. | ai | |
| dependencies | unvetted-dep:@primeuix/forms | AI (dependencies): First-party sibling package from same PrimeTek monorepo. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 3 / 0 | |
| 4.5.5 | 3 / 0 | |
| 4.5.4 | 3 / 0 | |
| 4.5.3 | 3 / 0 | |
| 4.5.2 | 3 / 0 | |
| 4.5.1 | 3 / 0 | |
| 4.5.0 | 3 / 0 | |
| 4.4.1 | 3 / 0 | |
| 4.4.0 | 3 / 0 | |
| 4.3.9 | 3 / 0 | |
| 4.3.8 | 3 / 0 | |
| 4.3.7 | 3 / 0 | |
| 4.3.6 | 3 / 0 | |
| 4.3.5 | 3 / 0 | |
| 4.3.4 | 3 / 0 | |
| 4.3.3 | 3 / 0 | |
| 4.3.2 | 3 / 0 | |
| 4.3.1 | 3 / 0 | |
| 4.3.0 | 3 / 0 | |
| 4.2.5 | 3 / 0 | |
| 4.2.4 | 3 / 0 | |
| 4.2.3 | 3 / 0 | |
| 4.2.2 | 3 / 0 | |
| 4.2.1 | 3 / 0 | |
| 4.2.0 | 3 / 0 |
v5.0.0
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 (mert.sincan) than the most recent previously approved version (tugcekucukoglu) on 2026-07-15, but mert.sincan 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.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.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 (tugcekucukoglu) than the most recent previously approved version (mert.sincan) on 2024-11-22, but tugcekucukoglu 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.
v4.2.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 (tugcekucukoglu) than the most recent previously approved version (mert.sincan) on 2024-11-14, but tugcekucukoglu 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.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.