reflinks MIT 18 versions

reflinks

npm Repository Homepage

Generate (relative) reference links for a glob of markdown files, allowing you to more easily create references from one file to another.

18

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

doowbjonschlinkert

Keywords

linklinksmarkdownmdreferencereflinkreflinks

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:lazy-cache	AI (phantom-deps): jonschlinkert packages use lazy-cache for deferred loading; deps are declared but not directly imported by design. Stable false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:log-utils	AI (phantom-deps): Loaded via lazy-cache pattern; static analysis won't detect the import. Stable false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:pkg-cache	AI (phantom-deps): Loaded via lazy-cache pattern; static analysis won't detect the import. Stable false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:time-diff	AI (phantom-deps): Loaded via lazy-cache pattern; static analysis won't detect the import. Stable false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:pkg-homepage	AI (phantom-deps): Loaded via lazy-cache pattern; static analysis won't detect the import. Stable false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:markdown-reference	AI (phantom-deps): Loaded via lazy-cache pattern; static analysis won't detect the import. Stable false positive for this package.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
1.0.0	6 / 2	2018-05-30
0.3.6	8 / 2	2018-05-29
0.3.5	9 / 7	2016-12-29
0.3.4	9 / 7	2016-07-18
0.3.3	9 / 7	2016-07-14
0.3.2	11 / 7	2016-07-13
0.3.1	10 / 7	2016-07-13
0.3.0	10 / 7	2016-07-13
0.2.7	7 / 7	2016-06-03
0.2.6	6 / 7	2016-05-03
0.2.5	6 / 7	2016-05-03
0.2.4	7 / 7	2016-04-27
0.2.3	7 / 7	2016-04-27
0.2.2	5 / 7	2016-04-22
0.2.1	5 / 7	2016-04-21
0.2.0	5 / 7	2016-04-21
0.1.2	3 / 3	2016-01-02
0.1.0	3 / 2	2015-03-06

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.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.