@push.rocks/smartlog
16
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
lossless
Keywords
logginglog managementtypescriptcentralized loggingjson loggingnode.jsdistributed systemsextensible logginglog routingconsole logginglog destinationslog levelserror trackingdevelopment tools
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@push.rocks/smartfile | AI (dependencies): Sibling package from same @push.rocks org/publisher; consistent ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@push.rocks/smarthash | AI (dependencies): Sibling package from same @push.rocks org/publisher; consistent ecosystem pattern. | ai | |
| dependencies | unvetted-dep:@push.rocks/smarttime | AI (dependencies): Sibling package from same @push.rocks org/publisher; consistent ecosystem pattern. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher has no provenance attestation history but is otherwise clean. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.2.2 | 9 / 5 | |
| 3.2.1 | 10 / 5 | |
| 3.2.0 | 10 / 5 | |
| 3.1.11 | 10 / 5 | |
| 3.1.10 | 10 / 5 | |
| 3.1.9 | 10 / 5 | |
| 3.1.8 | 10 / 5 | |
| 3.1.7 | 10 / 5 | |
| 3.1.3 | 10 / 5 | |
| 3.1.2 | 10 / 5 | |
| 3.1.1 | 10 / 6 | |
| 3.0.9 | 11 / 6 | |
| 3.0.8 | 11 / 6 | |
| 3.0.7 | 2 / 6 | |
| 3.0.6 | 2 / 6 | |
| 3.0.5 | 2 / 6 |
v3.0.7
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.