@gem-sdk/components
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is consistent across all versions; not a risk signal for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @gem-sdk packages consistently lack metadata (description, repo, keywords) — org-wide pattern, not a malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-wide pattern; no description across all @gem-sdk packages. | ai | |
| phantom-deps | phantom-dep:node-html-parser | AI (phantom-deps): node-html-parser is a declared runtime dep; phantom-dep heuristic fires on config-only references but dep is legitimate. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 5 / 12 | |
| 17.1.3 | 5 / 12 | |
| 17.1.2 | 5 / 12 | |
| 17.1.1 | 5 / 12 | |
| 17.1.0 | 5 / 12 | |
| 17.0.4 | 5 / 12 | |
| 17.0.3 | 5 / 12 | |
| 17.0.2 | 5 / 12 | |
| 17.0.0 | 5 / 12 | |
| 16.3.4 | 5 / 12 | |
| 16.3.3 | 5 / 12 | |
| 16.3.1 | 5 / 12 | |
| 16.3.0 | 5 / 12 | |
| 16.2.0 | 5 / 12 | |
| 16.0.4 | 5 / 12 | |
| 16.0.3 | 5 / 12 | |
| 16.0.2 | 5 / 12 | |
| 16.0.1 | 5 / 12 | |
| 16.0.0 | 5 / 12 |
v17.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.