@websolutespa/bom-cli
BOM cli of the BOM Repository
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): env-spread is in a setEnvVars helper that passes env to child processes — standard CLI pattern, not exfiltration. | ai | |
| phantom-deps | phantom-dep:nodemon | AI (phantom-deps): nodemon is listed as a runtime dep and referenced in scripts; phantom-dep heuristic is a false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher with 27 approved packages; lack of provenance is common and not a disqualifier here. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 14 / 12 | |
| 3.0.0 | 14 / 12 | |
| 2.0.0 | 14 / 12 | |
| 1.10.2 | 14 / 12 | |
| 1.10.0 | 14 / 12 | |
| 1.8.9 | 14 / 12 | |
| 1.8.8 | 14 / 12 | |
| 1.8.7 | 15 / 12 | |
| 1.8.6 | 15 / 12 | |
| 1.8.5 | 15 / 12 | |
| 1.8.4 | 15 / 12 | |
| 1.8.3 | 15 / 12 | |
| 1.8.2 | 15 / 12 | |
| 1.8.1 | 15 / 12 | |
| 1.8.0 | 15 / 12 | |
| 1.7.8 | 15 / 12 | |
| 1.7.7 | 15 / 12 | |
| 1.7.6 | 15 / 12 | |
| 1.7.5 | 15 / 12 | |
| 1.7.4 | 15 / 12 | |
| 1.7.3 | 14 / 12 | |
| 1.7.2 | 14 / 12 | |
| 1.7.1 | 14 / 12 | |
| 1.7.0 | 14 / 12 |
v1.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.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.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.