@danske/sapphire-css
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): Internal corporate package; provenance absence is consistent across all 77 versions. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Proprietary Danske Bank license; stable across all versions of this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 50.2.1 | 1 / 24 | |
| 50.1.0 | 1 / 24 | |
| 49.1.0 | 1 / 24 | |
| 49.0.0 | 1 / 24 | |
| 48.0.1 | 1 / 24 | |
| 48.0.0 | 1 / 24 | |
| 47.0.0 | 1 / 24 | |
| 46.0.1 | 1 / 24 | |
| 46.0.0 | 1 / 24 | |
| 45.1.0 | 1 / 24 | |
| 45.0.0 | 1 / 24 |
v50.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v50.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v49.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v49.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v48.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v47.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v46.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v45.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v45.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.