@gem-sdk/plugin-cookie-bar
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo plugin; sparse metadata is a consistent pattern across all @gem-sdk packages, not a malice indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @gem-sdk monorepo style; not indicative of malicious intent. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 16.0.0 | 0 / 2 | |
| 13.1.0 | 0 / 2 | |
| 13.0.0 | 0 / 2 | |
| 11.2.0 | 0 / 2 | |
| 7.0.0 | 0 / 2 |
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.