← Home

@primevue/auto-import-resolver

npm Homepage
35
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

tugcekucukoglucagatay.civicimert.sincan

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Legitimate PrimevVue monorepo sub-package; minimal metadata and tiny payload are expected for this utility resolver. ai
npm-metadata no-description AI (npm-metadata): Scoped monorepo package; missing description is a known pattern for PrimevVue sub-packages. ai
dependencies unvetted-dep:@primevue/metadata AI (dependencies): Sibling package from the same PrimevVue monorepo; not a third-party risk. ai

Versions (showing 35 of 35)

Version Deps Published
5.0.0 1 / 0
4.5.5 1 / 0
4.5.4 1 / 0
4.5.3 1 / 0
4.5.2 1 / 0
4.5.1 1 / 0
4.5.0 1 / 0
4.4.1 1 / 0
4.4.0 1 / 0
4.3.9 1 / 0
4.3.8 1 / 0
4.3.7 1 / 0
4.3.6 1 / 0
4.3.5 1 / 0
4.3.4 1 / 0
4.3.3 1 / 0
4.3.2 1 / 0
4.3.1 1 / 0
4.3.0 1 / 0
4.2.5 1 / 0
4.2.4 1 / 0
4.2.3 1 / 0
4.2.2 1 / 0
4.2.1 1 / 0
4.2.0 1 / 0
4.1.1 1 / 0
4.1.0 1 / 0
4.0.7 1 / 0
4.0.6 1 / 0
4.0.5 1 / 0
4.0.4 1 / 0
4.0.3 1 / 0
4.0.2 1 / 0
4.0.1 1 / 0
4.0.0 1 / 0

v5.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tugcekucukoglu → mert.sincan (on 2026-07-15, known maintainer) provenance

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.3.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tugcekucukoglu → mert.sincan (on 2024-11-01, known maintainer) provenance

This version was published by a different npm account (mert.sincan) than the most recent previously approved version (tugcekucukoglu) on 2024-11-01, 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.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

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.

v4.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.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.