@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, so a manually published version cannot be tied back to a reviewed commit.
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 83 of 83)
| Version | Deps | Published |
|---|---|---|
| 19.0.1 | 4 / 11 | |
| 19.0.0 | 4 / 11 | |
| 18.5.2 | 4 / 11 | |
| 18.5.1 | 4 / 11 | |
| 18.5.0 | 4 / 11 | |
| 18.4.6 | 4 / 11 | |
| 18.4.5 | 4 / 11 | |
| 18.4.4 | 4 / 11 | |
| 18.4.3 | 4 / 11 | |
| 18.4.2 | 4 / 11 | |
| 18.4.1 | 4 / 11 | |
| 18.3.0 | 4 / 11 | |
| 18.0.2 | 4 / 11 | |
| 18.0.0 | 4 / 11 | |
| 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 | |
| 15.0.6 | 5 / 14 | |
| 15.0.4 | 5 / 14 | |
| 15.0.3 | 5 / 14 | |
| 15.0.2 | 5 / 14 | |
| 15.0.1 | 5 / 14 | |
| 15.0.0 | 5 / 14 | |
| 14.0.1 | 5 / 14 | |
| 14.0.0 | 5 / 14 | |
| 13.2.3 | 5 / 14 | |
| 13.2.2 | 5 / 14 | |
| 13.2.1 | 5 / 14 | |
| 13.1.6 | 5 / 14 | |
| 13.1.5 | 5 / 14 | |
| 13.1.4 | 5 / 14 | |
| 13.1.3 | 5 / 14 | |
| 13.1.2 | 5 / 14 | |
| 13.1.1 | 5 / 14 | |
| 13.1.0 | 5 / 14 | |
| 13.0.0 | 5 / 14 | |
| 12.0.5 | 5 / 14 | |
| 12.0.3 | 5 / 14 | |
| 12.0.2 | 5 / 14 | |
| 12.0.1 | 5 / 14 | |
| 12.0.0 | 5 / 14 | |
| 11.2.5 | 5 / 14 | |
| 11.2.4 | 5 / 14 | |
| 11.2.3 | 5 / 14 | |
| 11.2.2 | 5 / 14 | |
| 11.2.1 | 5 / 14 | |
| 11.2.0 | 5 / 14 | |
| 10.0.2 | 5 / 14 | |
| 10.0.1 | 5 / 14 | |
| 10.0.0 | 5 / 14 | |
| 9.0.1 | 5 / 14 | |
| 9.0.0 | 5 / 14 | |
| 8.0.3 | 5 / 14 | |
| 8.0.2 | 5 / 14 | |
| 8.0.1 | 5 / 14 | |
| 8.0.0 | 5 / 14 | |
| 7.1.0 | 5 / 14 | |
| 7.0.5 | 5 / 14 | |
| 7.0.4 | 5 / 14 | |
| 7.0.2 | 5 / 14 | |
| 7.0.1 | 5 / 14 | |
| 7.0.0 | 5 / 14 | |
| 6.0.6 | 5 / 6 | |
| 6.0.5 | 5 / 6 | |
| 6.0.3 | 5 / 6 | |
| 6.0.2 | 5 / 6 | |
| 6.0.1 | 5 / 6 |
v19.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.