@bobfrankston/msgcommon
33
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
bobfrankston
Keywords
cliargument-parsermsgviewmsger
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:windows-shortcuts | AI (dependencies): windows-shortcuts is a legitimate npm package for Windows shortcut creation; its use in a CLI tool is expected and not suspicious. | ai | |
| phantom-deps | phantom-dep:@bobfrankston/msgcommon | AI (phantom-deps): Package lists itself as a dependency — likely a development artifact or versioning quirk. Same org scope, no security implication. | ai | |
| dependencies | unvetted-dep:@bobfrankston/msgcommon | AI (dependencies): Self-referential dependency from same author/org; benign quirk, not a supply chain risk. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.1.35 | 4 / 2 | |
| 0.1.34 | 4 / 2 | |
| 0.1.33 | 4 / 2 | |
| 0.1.32 | 4 / 2 | |
| 0.1.31 | 4 / 2 | |
| 0.1.30 | 4 / 2 | |
| 0.1.29 | 4 / 2 | |
| 0.1.28 | 3 / 2 | |
| 0.1.27 | 3 / 2 | |
| 0.1.24 | 3 / 2 | |
| 0.1.23 | 3 / 2 | |
| 0.1.22 | 3 / 2 | |
| 0.1.21 | 3 / 2 | |
| 0.1.20 | 3 / 2 | |
| 0.1.19 | 3 / 2 | |
| 0.1.18 | 3 / 2 | |
| 0.1.17 | 3 / 2 | |
| 0.1.16 | 3 / 2 | |
| 0.1.15 | 3 / 2 | |
| 0.1.14 | 3 / 2 | |
| 0.1.13 | 3 / 2 | |
| 0.1.12 | 3 / 2 | |
| 0.1.11 | 3 / 2 | |
| 0.1.10 | 3 / 2 | |
| 0.1.9 | 3 / 2 | |
| 0.1.8 | 3 / 2 | |
| 0.1.7 | 3 / 2 | |
| 0.1.6 | 2 / 2 | |
| 0.1.5 | 1 / 2 | |
| 0.1.4 | 1 / 2 | |
| 0.1.3 | 1 / 2 | |
| 0.1.2 | 1 / 2 | |
| 0.1.1 | 1 / 2 |
v0.1.35
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.