← Home

@quintype/arrow

Quintype's UI Component Library for Publisher Apps

51
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

devops-quintypesharangjsrajesh636bindiyareena07111996harshie46mauliksharmarakshi059veena.yemmiganurarunabhthakur94vishwanath.reddynandakishoremohammedshoaibsaiteja8494divyaprithvimanu6010athul_rajanavya-kedlaya

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:country-telephone-data AI (dependencies): Static country-code data package, no install scripts or network calls. ai
publish-pattern new-deps-added AI (publish-pattern): Legitimate UI library dependency, not a supply-chain vector. ai
phantom-deps phantom-dep:date-fns AI (phantom-deps): date-fns is explicitly declared in both dependencies and peerDependencies; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:date-fns-tz AI (phantom-deps): date-fns-tz is explicitly declared in both dependencies and peerDependencies; phantom-dep heuristic is a false positive here. ai

Versions (showing 51 of 225)

View all versions
Version Deps Published
3.54.21 11 / 0
3.54.20 10 / 0
3.54.19 10 / 0
3.54.18 10 / 0
3.54.17 10 / 0
3.54.16 10 / 0
3.54.15 10 / 0
3.54.14 10 / 0
3.54.13 10 / 0
3.54.12 10 / 0
3.54.11 10 / 0
3.54.10 10 / 0
3.54.9 10 / 0
3.54.8 10 / 0
3.54.7 10 / 0
3.54.5 10 / 0
3.54.4 10 / 0
3.54.3 10 / 0
3.54.2 10 / 0
3.54.0 10 / 0
3.53.6 10 / 0
3.53.5 10 / 0
3.53.4 10 / 0
3.53.3 10 / 0
3.53.1 10 / 0
3.53.0 10 / 0
3.52.5 10 / 0
3.52.4 10 / 0
3.52.3 10 / 0
3.52.2 10 / 0
3.52.0 10 / 0
3.51.10 10 / 0
3.51.9 10 / 0
3.51.8 10 / 0
3.51.7 10 / 0
3.51.6 10 / 0
3.51.5 10 / 0
3.51.4 10 / 0
3.51.3 10 / 0
3.51.2 10 / 0
3.51.1 10 / 0
3.51.0 10 / 0
3.50.1 10 / 0
3.50.0 10 / 0
3.49.5 10 / 0
3.49.4 10 / 0
3.49.3 10 / 0
3.49.2 10 / 0
3.49.1 10 / 0
3.49.0 10 / 0
3.48.1 10 / 0

v3.54.21

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: mohammedshoaib → veena.yemmiganur (on 2026-07-10, known maintainer) provenance

This version was published by a different npm account (veena.yemmiganur) than the most recent previously approved version (mohammedshoaib) on 2026-07-10, but veena.yemmiganur 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.

v3.54.20

1 finding
LOW No provenance attestation provenance

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

v3.54.19

1 finding
LOW No provenance attestation provenance

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

v3.51.2

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: reena07111996 → vishwanath.reddy (on 2025-04-23, known maintainer) provenance

This version was published by a different npm account (vishwanath.reddy) than the most recent previously approved version (reena07111996) on 2025-04-23, but vishwanath.reddy 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.

v3.51.1

1 finding
LOW No provenance attestation provenance

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

v3.51.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: vishwanath.reddy → reena07111996 (on 2025-04-17, known maintainer) provenance

This version was published by a different npm account (reena07111996) than the most recent previously approved version (vishwanath.reddy) on 2025-04-17, but reena07111996 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.

v3.50.1

1 finding
LOW No provenance attestation provenance

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

v3.50.0

1 finding
LOW No provenance attestation provenance

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

v3.49.5

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: vishwanath.reddy → reena07111996 (on 2025-02-20, known maintainer) provenance

This version was published by a different npm account (reena07111996) than the most recent previously approved version (vishwanath.reddy) on 2025-02-20, but reena07111996 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.

v3.49.4

1 finding
LOW No provenance attestation provenance

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

v3.49.3

1 finding
LOW No provenance attestation provenance

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

v3.49.2

1 finding
LOW No provenance attestation provenance

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

v3.49.1

1 finding
LOW No provenance attestation provenance

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

v3.49.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: reena07111996 → vishwanath.reddy (on 2024-10-30, known maintainer) provenance

This version was published by a different npm account (vishwanath.reddy) than the most recent previously approved version (reena07111996) on 2024-10-30, but vishwanath.reddy 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.

v3.48.1

1 finding
LOW No provenance attestation provenance

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