captains-log
Lightweight logger with a simple pass-through configuration for use with fancier logging libraries
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from mikermcneil to rachaelshaw is a documented, legitimate org-level transition within the Balderdashy/Sails.js team. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): rachaelshaw is a long-standing Sails.js org member with 751 approved packages; addition reflects a legitimate org-level maintainer transition. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.0.5 | 4 / 2 | |
| 2.0.4 | 4 / 2 | |
| 2.0.3 | 4 / 2 | |
| 2.0.2 | 4 / 2 | |
| 2.0.1 | 4 / 2 | |
| 2.0.0 | 4 / 2 | |
| 1.0.3 | 3 / 2 | |
| 1.0.2 | 3 / 2 | |
| 1.0.1 | 3 / 2 | |
| 1.0.0 | 3 / 2 | |
| 0.11.11 | 4 / 2 | |
| 0.11.10 | 4 / 2 | |
| 0.11.9 | 4 / 2 | |
| 0.11.8 | 4 / 2 | |
| 0.11.7 | 4 / 2 | |
| 0.11.6 | 4 / 1 | |
| 0.11.5 | 4 / 1 | |
| 0.11.1 | 4 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.6 | 3 / 1 | |
| 0.10.5 | 3 / 1 | |
| 0.10.4 | 3 / 1 | |
| 0.10.3 | 3 / 1 | |
| 0.10.0 | 2 / 2 |
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-07-21. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-09. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2019-04-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-08-01. This could indicate a legitimate maintainer transition or an account compromise.