logfire
JavaScript API for Logfire - https://pydantic.dev/logfire
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pydantic/logfire-api | AI (dependencies): Sibling package from the same Pydantic org; expected monorepo dependency pattern. | ai | |
| source-diff | obfuscated-file:dist/logfireApiConfig-BNBplQH8.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; readable OTel instrumentation code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/vars.cjs | AI (source-diff): Standard Vite/Rollup minified bundle output; readable OTel instrumentation code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/logfireApiConfig-nMrOSvHr.js | AI (source-diff): Standard Vite/Rollup minified bundle output; readable OTel instrumentation code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Bundled into dist output by Vite; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Bundled into dist output by Vite; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:p-retry | AI (phantom-deps): Bundled into dist output by Vite; not directly imported at runtime. | ai | |
| source-diff | obfuscated-file:dist/vars.js | AI (source-diff): Standard Vite/Rollup minified bundle output; readable OTel instrumentation code, not obfuscation. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation provides stronger integrity guarantee than gitHead; acceptable for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.15.1 | 3 / 7 | |
| 0.15.0 | 3 / 7 | |
| 0.14.0 | 3 / 7 | |
| 0.13.2 | 0 / 3 | |
| 0.13.1 | 0 / 3 | |
| 0.13.0 | 0 / 3 | |
| 0.12.0 | 0 / 3 | |
| 0.11.1 | 0 / 10 | |
| 0.11.0 | 0 / 8 | |
| 0.10.0 | 2 / 18 | |
| 0.8.0 | 1 / 18 | |
| 0.7.0 | 1 / 18 | |
| 0.6.0 | 1 / 17 | |
| 0.5.1 | 1 / 17 | |
| 0.5.0 | 1 / 17 |
v0.15.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.