@enervance/insight-cim-model
CIM data model
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@fast-csv/parse | AI (phantom-deps): Declared dep likely used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@turf/clusters-dbscan | AI (phantom-deps): Turf sub-module declared for runtime use; stable false positive. | ai | |
| phantom-deps | phantom-dep:@turf/line-to-polygon | AI (phantom-deps): Turf sub-module declared for runtime use; stable false positive. | ai | |
| phantom-deps | phantom-dep:@turf/point-to-line-distance | AI (phantom-deps): Turf sub-module declared for runtime use; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.29 | 16 / 26 | |
| 1.0.28 | 16 / 26 | |
| 1.0.22 | 16 / 26 | |
| 1.0.20 | 16 / 26 | |
| 1.0.18 | 16 / 26 | |
| 1.0.16 | 16 / 26 | |
| 1.0.12 | 16 / 26 | |
| 1.0.10 | 16 / 26 |
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
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.20
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.16
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.