@developer-overheid-nl/don-register-components
The components for the API- and OSS registers
1
Versions
EUPL-1.2
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
joostfarlapasibunsetonix
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rijkshuisstijl-community/design-tokens | AI (phantom-deps): CSS/design-token package loaded by convention in config files, not direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rijkshuisstijl-community/components-css | AI (phantom-deps): CSS package referenced in config files; not directly imported by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/parse-link-header | AI (phantom-deps): Type-only package loaded by TypeScript convention, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:parse-link-header | AI (phantom-deps): Referenced in config files; phantom-dep heuristic fires on indirect usage patterns; stable false positive. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 11 / 5 |
v1.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.