@parhelia/alpaca
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@graphiql/plugin-explorer | AI (dependencies): @graphiql/plugin-explorer is a well-known GraphQL explorer plugin; stable legitimate dependency for this UI package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is a scoped UI component library under active development; missing metadata is sloppy but not indicative of malice. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is a build-time dep used in config files; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom referenced in config/type context; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:@uiw/react-textarea-code-editor | AI (phantom-deps): Likely re-exported or used indirectly; stable false positive for this package. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 0.1.12882 | 11 / 9 | |
| 0.1.12881 | 11 / 9 | |
| 0.1.12880 | 11 / 9 | |
| 0.1.12879 | 11 / 9 | |
| 0.1.12877 | 11 / 9 | |
| 0.1.12876 | 11 / 9 | |
| 0.1.12875 | 11 / 9 | |
| 0.1.12870 | 11 / 9 | |
| 0.1.12868 | 11 / 9 | |
| 0.1.12856 | 11 / 9 | |
| 0.1.12844 | 11 / 9 | |
| 0.1.12843 | 11 / 9 | |
| 0.1.12841 | 11 / 9 | |
| 0.1.12839 | 11 / 9 | |
| 0.1.12838 | 11 / 9 | |
| 0.1.12836 | 11 / 9 | |
| 0.1.12783 | 11 / 9 | |
| 0.1.12782 | 11 / 9 | |
| 0.1.12781 | 11 / 9 | |
| 0.1.12780 | 11 / 9 | |
| 0.1.12777 | 11 / 9 | |
| 0.1.12776 | 11 / 9 | |
| 0.1.12775 | 11 / 9 | |
| 0.1.12774 | 11 / 9 | |
| 0.1.12772 | 11 / 9 | |
| 0.1.12767 | 11 / 9 | |
| 0.1.12766 | 11 / 9 | |
| 0.1.12763 | 11 / 9 | |
| 0.1.12762 | 11 / 9 | |
| 0.1.12760 | 11 / 9 | |
| 0.1.12758 | 11 / 9 | |
| 0.1.12756 | 11 / 9 | |
| 0.1.12755 | 11 / 9 | |
| 0.1.12752 | 11 / 9 | |
| 0.1.12749 | 11 / 9 | |
| 0.1.12744 | 11 / 9 | |
| 0.1.12741 | 11 / 9 | |
| 0.1.12737 | 11 / 9 | |
| 0.1.12730 | 11 / 9 | |
| 0.1.12719 | 11 / 9 | |
| 0.1.12710 | 11 / 9 | |
| 0.1.12705 | 11 / 9 | |
| 0.1.12694 | 11 / 9 | |
| 0.1.12676 | 11 / 9 | |
| 0.1.12663 | 11 / 9 | |
| 0.1.12638 | 11 / 9 | |
| 0.1.12636 | 11 / 9 | |
| 0.1.12632 | 11 / 9 | |
| 0.1.12614 | 11 / 9 | |
| 0.1.12612 | 11 / 9 | |
| 0.1.12601 | 11 / 9 |
v0.1.12882
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12881
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12880
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12879
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12877
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12876
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12875
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12870
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12868
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12856
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12844
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12843
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12841
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12839
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12838
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12836
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 (majensen) than the most recent previously approved version (muentingah) on 2026-05-30, but majensen 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.
v0.1.12783
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12782
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12781
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 (muentingah) than the most recent previously approved version (trackway) on 2026-05-09, but muentingah 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.
v0.1.12780
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 (muentingah) than the most recent previously approved version (trackway) on 2026-05-08, but muentingah 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.
v0.1.12777
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12776
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12775
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12774
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12772
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12767
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12766
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12763
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12762
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12760
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12758
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12756
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12755
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12752
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12749
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12744
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12741
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12730
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12719
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12710
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12705
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12694
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12676
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12663
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12638
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12636
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12632
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12614
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12612
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12601
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.