@baseplate-dev/plugin-observability
Observability plugins for Baseplate (Sentry error monitoring, performance tracking)
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/web/assets/__federation_shared_@baseplate-dev/project-builder-lib-BEoACZXa.js | AI (source-diff): Standard Vite module-federation minified bundle; sample shows readable imports and JSDoc, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance attestation; legitimate automation change. | ai | |
| source-diff | obfuscated-file:dist/web/assets/__federation_shared_@baseplate-dev/project-builder-lib-DQAPSZRY.js | AI (source-diff): Standard Vite module-federation bundle artifact; long lines are minified but readable imports, not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are first-party @baseplate-dev packages or well-known libs (react, zod); consistent with plugin expansion. | ai | |
| phantom-deps | phantom-dep:react-hook-form | AI (phantom-deps): react-hook-form declared as dep for plugin UI; referenced in config/templates, not directly imported in main TS sources. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Plugin package ships static templates; near-empty dist/index.js and minimal README are expected for this package type. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom declared as dep for plugin UI; not directly imported in TS sources but used via bundled Vite output. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.6.9 | 12 / 17 | |
| 0.6.8 | 12 / 17 | |
| 0.6.7 | 12 / 17 | |
| 0.0.1 | 0 / 0 |
v0.6.8
3 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
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.6.7
3 findingsThis version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.
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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.