@onlineapps/monitoring-core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves from a controlled 'available' map of OpenTelemetry instrumentation modules — not user-supplied arbitrary input. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): winston is a declared dependency used indirectly via the monitoring stack; phantom-dep heuristic fires incorrectly. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-node | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation-http | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation-mysql2 | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation-express | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/instrumentation-redis-4 | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-proto | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-metrics-otlp-proto | AI (phantom-deps): OpenTelemetry packages loaded dynamically via instrumentation loader; false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.0.23 | 19 / 2 | |
| 1.0.22 | 19 / 2 | |
| 1.0.21 | 19 / 2 | |
| 1.0.20 | 19 / 2 | |
| 1.0.19 | 19 / 2 | |
| 1.0.18 | 19 / 2 | |
| 1.0.17 | 19 / 2 | |
| 1.0.16 | 19 / 2 | |
| 1.0.15 | 18 / 2 | |
| 1.0.14 | 18 / 2 | |
| 1.0.13 | 18 / 2 | |
| 1.0.12 | 18 / 2 | |
| 1.0.11 | 18 / 2 | |
| 1.0.10 | 18 / 2 | |
| 1.0.9 | 17 / 2 | |
| 1.0.8 | 17 / 2 | |
| 1.0.6 | 17 / 2 | |
| 1.0.4 | 17 / 2 | |
| 1.0.3 | 17 / 2 | |
| 1.0.1 | 16 / 2 | |
| 1.0.0 | 16 / 2 |
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.