chainy-plugin-feed
Chainy action that sets the chain data with the parsed results of a request, includes caching
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): balupton's chainy-plugin-* packages use 0.0.0 as a legitimate initial version; this is a known pattern for this author's plugin ecosystem, not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is consistent with a 4359-day-old minimal plugin stub by a highly trusted publisher (balupton). Not a spam or malicious package. | ai |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.