hyparquet
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Established handoff to severo_bo (99 approved), consistent for a year; stable across versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same legitimate maintainer transition; already vetted across many versions. | ai |
Versions (showing 51 of 85)
| Version | Deps | Published |
|---|---|---|
| 1.26.2 | 0 / 7 | |
| 1.26.1 | 0 / 7 | |
| 1.26.0 | 0 / 7 | |
| 1.25.8 | 0 / 7 | |
| 1.25.7 | 0 / 7 | |
| 1.25.6 | 0 / 7 | |
| 1.25.5 | 0 / 7 | |
| 1.25.4 | 0 / 7 | |
| 1.25.3 | 0 / 7 | |
| 1.25.2 | 0 / 7 | |
| 1.25.1 | 0 / 7 | |
| 1.25.0 | 0 / 7 | |
| 1.24.1 | 0 / 7 | |
| 1.24.0 | 0 / 7 | |
| 1.23.3 | 0 / 7 | |
| 1.23.2 | 0 / 7 | |
| 1.23.1 | 0 / 7 | |
| 1.23.0 | 0 / 7 | |
| 1.22.1 | 0 / 7 | |
| 1.22.0 | 0 / 7 | |
| 1.21.1 | 0 / 7 | |
| 1.21.0 | 0 / 7 | |
| 1.20.3 | 0 / 7 | |
| 1.20.2 | 0 / 7 | |
| 1.20.1 | 0 / 7 | |
| 1.20.0 | 0 / 7 | |
| 1.19.0 | 0 / 7 | |
| 1.18.1 | 0 / 7 | |
| 1.18.0 | 0 / 7 | |
| 1.17.8 | 0 / 7 | |
| 1.17.7 | 0 / 7 | |
| 1.17.6 | 0 / 7 | |
| 1.17.5 | 0 / 7 | |
| 1.17.4 | 0 / 7 | |
| 1.17.3 | 0 / 7 | |
| 1.17.2 | 0 / 7 | |
| 1.17.1 | 0 / 7 | |
| 1.17.0 | 0 / 7 | |
| 1.16.2 | 0 / 7 | |
| 1.16.1 | 0 / 8 | |
| 1.16.0 | 0 / 8 | |
| 1.15.0 | 0 / 8 | |
| 1.14.0 | 0 / 8 | |
| 1.13.6 | 0 / 8 | |
| 1.13.5 | 0 / 8 | |
| 1.13.4 | 0 / 8 | |
| 1.13.3 | 0 / 8 | |
| 1.13.2 | 0 / 8 | |
| 1.13.1 | 0 / 8 | |
| 1.13.0 | 0 / 8 | |
| 1.12.1 | 0 / 8 |
v1.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.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 (severo_bo) than the most recent previously approved version (platypii) on 2025-10-16, but severo_bo 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.
v1.17.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 (severo_bo) than the most recent previously approved version (platypii) on 2025-09-09, but severo_bo 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.
v1.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.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 (severo_bo) than the most recent previously approved version (platypii) on 2025-08-18, but severo_bo 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.
v1.17.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 (severo_bo) than the most recent previously approved version (platypii) on 2025-08-15, but severo_bo 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.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.