@bobfrankston/miscassists
Miscelleanous assists for various tasks including defining port numbers
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Long-lived personal utility package; empty description is a style choice, not a malware signal. | ai | |
| phantom-deps | phantom-dep:esm | AI (phantom-deps): esm is declared as a runtime dependency; phantom-dep heuristic fires because it's referenced via config rather than direct import. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 1.0.56 | 2 / 1 | |
| 1.0.55 | 2 / 1 | |
| 1.0.54 | 2 / 1 | |
| 1.0.53 | 2 / 1 | |
| 1.0.52 | 2 / 1 | |
| 1.0.50 | 2 / 1 | |
| 1.0.42 | 1 / 1 | |
| 1.0.41 | 1 / 1 | |
| 1.0.39 | 1 / 1 | |
| 1.0.38 | 1 / 1 | |
| 1.0.37 | 1 / 1 | |
| 1.0.36 | 1 / 1 | |
| 1.0.35 | 1 / 1 | |
| 1.0.34 | 1 / 1 | |
| 1.0.33 | 1 / 1 | |
| 1.0.27 | 1 / 1 | |
| 1.0.26 | 1 / 1 | |
| 1.0.24 | 1 / 1 | |
| 1.0.23 | 1 / 1 | |
| 1.0.22 | 1 / 1 | |
| 1.0.21 | 1 / 1 | |
| 1.0.20 | 1 / 1 | |
| 1.0.19 | 1 / 1 | |
| 1.0.18 | 1 / 1 | |
| 1.0.17 | 1 / 1 | |
| 1.0.16 | 1 / 1 | |
| 1.0.15 | 1 / 1 | |
| 1.0.13 | 1 / 1 | |
| 1.0.12 | 1 / 1 | |
| 1.0.11 | 2 / 0 | |
| 1.0.10 | 2 / 0 | |
| 1.0.9 | 2 / 0 | |
| 1.0.8 | 2 / 0 | |
| 1.0.7 | 2 / 0 | |
| 1.0.5 | 2 / 0 | |
| 1.0.3 | 2 / 0 |
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.