@loglayer/transport-tslog
Supply chain provenance
Status for the latest visible version.
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): Maintainer migrated to GitHub Actions CI publishing with SLSA attestation; consistent with automated pipeline adoption. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-attested publish in a monorepo transport package; no malicious indicators present. | ai | |
| provenance | no-provenance | AI (provenance): Loglayer monorepo does not publish with Sigstore provenance; stable pattern across versions. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 1 / 7 | |
| 4.0.3 | 1 / 7 | |
| 4.0.2 | 1 / 7 | |
| 4.0.1 | 1 / 7 | |
| 4.0.0 | 1 / 7 | |
| 3.0.13 | 1 / 7 | |
| 3.0.12 | 1 / 7 | |
| 3.0.11 | 1 / 7 | |
| 3.0.10 | 1 / 7 | |
| 3.0.9 | 1 / 7 | |
| 3.0.8 | 1 / 7 | |
| 3.0.7 | 1 / 7 | |
| 3.0.6 | 1 / 7 | |
| 3.0.5 | 1 / 7 |
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.