loglayer
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): Package migrated to GitHub Actions publishing with SLSA attestation; this is the expected new publisher going forward. | ai | |
| dependencies | unvetted-dep:@loglayer/plugin | AI (dependencies): First-party @loglayer scoped package from same monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@loglayer/shared | AI (dependencies): First-party @loglayer scoped package from same monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@loglayer/transport | AI (dependencies): First-party @loglayer scoped package from same monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@loglayer/context-manager | AI (dependencies): First-party @loglayer scoped package from same monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@loglayer/log-level-manager | AI (dependencies): First-party @loglayer scoped package from same monorepo; stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 9.3.0 | 5 / 5 | |
| 9.2.0 | 5 / 5 | |
| 9.1.1 | 5 / 5 | |
| 9.1.0 | 5 / 5 | |
| 9.0.1 | 5 / 5 | |
| 9.0.0 | 5 / 5 | |
| 8.5.0 | 5 / 5 | |
| 8.4.1 | 5 / 5 | |
| 8.4.0 | 5 / 5 | |
| 8.3.0 | 5 / 5 | |
| 8.2.0 | 5 / 5 | |
| 8.1.1 | 5 / 5 | |
| 8.1.0 | 5 / 5 | |
| 8.0.2 | 5 / 5 | |
| 8.0.1 | 5 / 5 | |
| 8.0.0 | 5 / 5 | |
| 7.2.1 | 4 / 5 | |
| 7.2.0 | 4 / 5 | |
| 7.1.0 | 4 / 5 | |
| 7.0.1 | 4 / 5 | |
| 7.0.0 | 4 / 5 |
v9.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.1
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.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.