@equinor/echo-framework
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): CI-published Equinor internal package; provenance absence is consistent across all 320 versions. | ai | |
| dependencies | unvetted-dep:ag-charts-react | AI (dependencies): ag-charts-react is a legitimate AG Grid charting library; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:ag-charts-enterprise | AI (dependencies): ag-charts-enterprise is a legitimate AG Grid charting library; stable dependency for this package. | ai | |
| phantom-deps | phantom-dep:dexie | AI (phantom-deps): Framework likely re-exports or conditionally uses dexie; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ag-charts-enterprise | AI (phantom-deps): ag-charts-enterprise may be re-exported or used in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mark.js | AI (phantom-deps): Framework likely re-exports or conditionally uses mark.js; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ag-charts-react | AI (phantom-deps): ag-charts-react may be re-exported or used in config; stable false positive for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 6.2.1 | 5 / 0 | |
| 6.2.0 | 5 / 0 | |
| 6.1.0 | 5 / 0 | |
| 6.0.0 | 5 / 0 | |
| 5.0.0 | 5 / 0 | |
| 4.3.2 | 5 / 0 | |
| 4.3.1 | 5 / 0 | |
| 4.3.0 | 5 / 0 | |
| 4.2.0 | 5 / 0 | |
| 4.1.1 | 5 / 0 | |
| 4.1.0 | 5 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 | |
| 3.1.0 | 5 / 0 | |
| 3.0.0 | 5 / 0 | |
| 2.4.3 | 5 / 0 | |
| 2.4.2 | 5 / 0 | |
| 2.4.1 | 5 / 0 | |
| 2.4.0 | 5 / 0 | |
| 2.3.0 | 5 / 0 | |
| 2.2.3 | 5 / 0 | |
| 2.2.2 | 5 / 0 | |
| 2.2.1 | 5 / 0 | |
| 2.2.0 | 5 / 0 |
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.