winston-transport
Base stream implementations for winston@3 and up.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher change is stale (1678d), matches long-standing legitimate transfer for this package. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-persisted publisher change, not consistent with takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Normal release cadence for mature, widely-used infra package. | ai | |
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): Vendored code-prettify.js in nyc coverage report; benign minified asset, not source. | ai | |
| provenance | no-provenance | AI (provenance): Established winston ecosystem package; lack of provenance attestation is common and not a security concern for this well-known package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.9.0 | 3 / 12 | |
| 4.8.1 | 3 / 12 | |
| 4.8.0 | 3 / 12 | |
| 4.7.1 | 3 / 12 | |
| 4.7.0 | 3 / 12 | |
| 4.6.0 | 3 / 12 | |
| 4.5.0 | 3 / 12 | |
| 4.4.2 | 3 / 11 | |
| 4.4.1 | 3 / 11 | |
| 4.4.0 | 2 / 11 | |
| 4.3.0 | 2 / 11 | |
| 4.2.0 | 2 / 8 | |
| 4.1.0 | 1 / 8 | |
| 4.0.0 | 1 / 8 |
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
2 findingsThis version was published by a different npm account (w-b-t) than the most recent previously approved version (dabh) on 2021-12-14. It has since remained available on npm for 1678 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
2 findingsThis version was published by a different npm account (dabh) than the most recent previously approved version (indexzero) on 2020-06-21. It has since remained available on npm for 2219 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.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.
v4.1.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.
v4.0.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.