@types/rfdc
Stub TypeScript definitions entry for rfdc, which provides its own types definitions
2
Versions
MIT
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
types
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Stub @types/ packages are intentionally minimal: no code, no README instructions, no repo link. These signals are structural false positives for this package type. | ai | |
| phantom-deps | phantom-dep:rfdc | AI (phantom-deps): Stub types packages declare a dep on the real package to forward its bundled types; no import is expected or needed. This is the correct pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Adding rfdc as a dependency is the entire purpose of this stub package — it forwards rfdc's bundled type definitions. Not an attack vector. | ai |
v1.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.