@quintype/arrow
Quintype's UI Component Library for Publisher Apps
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 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.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 |
v3.54.18
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 (mohammedshoaib) than the most recent previously approved version (veena.yemmiganur) on 2026-06-01, but mohammedshoaib 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.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.15
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 (veena.yemmiganur) than the most recent previously approved version (mohammedshoaib) on 2026-05-29, 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.14
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 (mohammedshoaib) than the most recent previously approved version (vishwanath.reddy) on 2026-05-15, but mohammedshoaib 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.13
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 (veena.yemmiganur) than the most recent previously approved version (vishwanath.reddy) on 2026-05-13, 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.12
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 (reena07111996) than the most recent previously approved version (vishwanath.reddy) on 2026-05-05, 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.54.11
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 (veena.yemmiganur) than the most recent previously approved version (vishwanath.reddy) on 2026-05-05, 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.10
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 (mohammedshoaib) than the most recent previously approved version (vishwanath.reddy) on 2026-05-04, but mohammedshoaib 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.8
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 (reena07111996) than the most recent previously approved version (veena.yemmiganur) on 2026-04-28, 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.54.7
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 (mohammedshoaib) than the most recent previously approved version (veena.yemmiganur) on 2026-04-24, but mohammedshoaib 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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.54.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 (veena.yemmiganur) than the most recent previously approved version (vishwanath.reddy) on 2026-03-24, 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.53.6
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 (veena.yemmiganur) than the most recent previously approved version (vishwanath.reddy) on 2026-03-11, 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.53.5
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 (veena.yemmiganur) than the most recent previously approved version (vishwanath.reddy) on 2026-03-09, 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.53.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.53.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.53.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 (veena.yemmiganur) than the most recent previously approved version (phaneendraandukuri) on 2025-10-14, 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.52.5
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 (reena07111996) than the most recent previously approved version (phaneendraandukuri) on 2025-07-15, 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.52.4
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 (vishwanath.reddy) than the most recent previously approved version (phaneendraandukuri) on 2025-07-03, 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.52.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 (vishwanath.reddy) than the most recent previously approved version (phaneendraandukuri) on 2025-06-29, 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.52.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 (reena07111996) than the most recent previously approved version (phaneendraandukuri) on 2025-06-27, 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.52.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 (reena07111996) than the most recent previously approved version (phaneendraandukuri) on 2025-06-27, 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.51.10
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 (vishwanath.reddy) than the most recent previously approved version (phaneendraandukuri) on 2025-06-27, 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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.51.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.51.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.51.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.51.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.51.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.51.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.