get-meta-file ISC 21 versions

get-meta-file

npm Repository Homepage

gets a meta file and its contents

21

Versions

ISC

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

mateodelnortepatrickleet

Keywords

get-meta-filemetareporepositorymetarepositorymetarepo

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): Package is 9+ years old with 21 versions and a legitimate ecosystem history; 0.0.0 is its genuine initial version, not a throwaway.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is the core functionality of this package — it loads a .meta config file from a resolved path. This is intentional design, not a security risk.	ai	2026/04/24
phantom-deps	phantom-dep:inquirer	AI (phantom-deps): inquirer is listed as a dependency but may be used indirectly or conditionally; not a security concern for this config-file utility.	ai	2026/04/24

Versions (showing 21 of 21)

Version	Deps	Published
1.3.6	6 / 8	2021-04-19
1.3.5	6 / 8	2021-04-16
1.3.4	6 / 8	2019-11-26
1.3.3	6 / 8	2019-07-14
1.3.2	6 / 8	2019-07-10
1.3.1	6 / 8	2019-06-14
1.3.0	6 / 8	2019-06-13
1.2.1	6 / 8	2019-06-12
1.2.0	6 / 3	2019-05-06
1.1.4	6 / 3	2019-01-09
1.1.3	6 / 3	2019-01-09
1.1.2	6 / 3	2018-12-30
1.1.1	6 / 3	2018-12-23
1.1.0	6 / 3	2018-12-22
1.0.0	5 / 3	2018-12-21
0.0.5	5 / 0	2017-08-30
0.0.4	4 / 0	2017-08-18
0.0.3	2 / 0	2017-08-11
0.0.2	2 / 0	2017-08-10
0.0.1	1 / 0	2017-04-25
0.0.0	1 / 0	2017-04-25

v1.3.6

1 finding

LOW No provenance attestation provenance

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

v1.3.5

1 finding

LOW No provenance attestation provenance

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

v1.3.4

1 finding

LOW No provenance attestation provenance

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

v1.3.3

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings

HIGH Publisher changed: mateodelnorte → patrickleet (on 2018-12-21) provenance

This version was published by a different npm account than previous versions on 2018-12-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

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.

v0.0.1

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.

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