@bobfrankston/rmfc
RMF Common Utilities
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 |
|---|---|---|---|---|
| vendored-integrity | unresolved-vendored-tree:tests/node_modules/@types/node | AI (vendored-integrity): Test-fixture node_modules dir, not a runtime payload. | ai | |
| vendored-integrity | unresolved-vendored-tree:tests/node_modules/esm | AI (vendored-integrity): Test-fixture node_modules dir, not a runtime payload. | ai | |
| dependencies | unvetted-dep:@bobfrankston/certsupport | AI (dependencies): Same-org first-party dependency by this long-tenured publisher. | ai | |
| phantom-deps | phantom-dep:@bobfrankston/certsupport | AI (phantom-deps): Same-org scope, expected pattern. | ai | |
| phantom-deps | phantom-dep:iconv-lite | AI (phantom-deps): Common encoding lib, plausibly used via require paths not scanned. | ai | |
| phantom-deps | phantom-dep:help | AI (phantom-deps): Small utility dep declared but used indirectly; long-tenured publisher, low risk. | ai | |
| phantom-deps | phantom-dep:node | AI (phantom-deps): Legacy declared dep, not a real import concern. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Standard type-only dep, loaded by convention. | ai | |
| semgrep | semgrep:silent-process-exec | AI (semgrep): reloadProgram() self-restarts the current process via argv[0]/argv[1]; not a reverse shell or miner. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same self-restart pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dependency. | ai | |
| phantom-deps | phantom-dep:@types/chalk | AI (phantom-deps): Type-only package; not directly imported at runtime by convention. | ai |
Versions (showing 66 of 166)
| Version | Deps | Published |
|---|---|---|
| 1.0.76 | 4 / 1 | |
| 1.0.75 | 4 / 1 | |
| 1.0.74 | 4 / 1 | |
| 1.0.72 | 4 / 1 | |
| 1.0.71 | 4 / 1 | |
| 1.0.70 | 4 / 1 | |
| 1.0.69 | 3 / 1 | |
| 1.0.68 | 3 / 1 | |
| 1.0.67 | 3 / 1 | |
| 1.0.66 | 3 / 1 | |
| 1.0.62 | 3 / 1 | |
| 1.0.61 | 3 / 1 | |
| 1.0.60 | 3 / 1 | |
| 1.0.59 | 3 / 1 | |
| 1.0.58 | 3 / 1 | |
| 1.0.57 | 3 / 1 | |
| 1.0.56 | 4 / 1 | |
| 1.0.55 | 4 / 1 | |
| 1.0.54 | 4 / 1 | |
| 1.0.51 | 5 / 1 | |
| 1.0.50 | 5 / 1 | |
| 1.0.49 | 5 / 1 | |
| 1.0.48 | 5 / 1 | |
| 1.0.47 | 5 / 1 | |
| 1.0.46 | 5 / 1 | |
| 1.0.45 | 5 / 1 | |
| 1.0.42 | 5 / 1 | |
| 1.0.41 | 5 / 1 | |
| 1.0.40 | 5 / 1 | |
| 1.0.39 | 5 / 1 | |
| 1.0.38 | 3 / 1 | |
| 1.0.37 | 3 / 1 | |
| 1.0.36 | 3 / 1 | |
| 1.0.35 | 3 / 1 | |
| 1.0.34 | 3 / 1 | |
| 1.0.32 | 3 / 1 | |
| 1.0.31 | 3 / 1 | |
| 1.0.30 | 3 / 1 | |
| 1.0.29 | 3 / 1 | |
| 1.0.28 | 3 / 1 | |
| 1.0.27 | 3 / 1 | |
| 1.0.26 | 3 / 1 | |
| 1.0.25 | 3 / 1 | |
| 1.0.24 | 3 / 1 | |
| 1.0.23 | 3 / 1 | |
| 1.0.22 | 2 / 1 | |
| 1.0.21 | 2 / 1 | |
| 1.0.20 | 2 / 1 | |
| 1.0.19 | 2 / 1 | |
| 1.0.18 | 2 / 1 | |
| 1.0.16 | 3 / 1 | |
| 1.0.15 | 3 / 1 | |
| 1.0.14 | 3 / 1 | |
| 1.0.13 | 3 / 1 | |
| 1.0.12 | 3 / 1 | |
| 1.0.11 | 3 / 1 | |
| 1.0.10 | 3 / 1 | |
| 1.0.9 | 3 / 1 | |
| 1.0.7 | 3 / 1 | |
| 1.0.6 | 3 / 1 | |
| 1.0.5 | 3 / 1 | |
| 1.0.4 | 2 / 0 | |
| 1.0.3 | 2 / 0 | |
| 1.0.2 | 2 / 0 | |
| 1.0.1 | 2 / 0 | |
| 1.0.0 | 2 / 0 |
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.