@univ-lehavre/atlas-researcher-profiles MIT 15 versions

@univ-lehavre/atlas-researcher-profiles

npm Repository Homepage

Researcher profiles service layer: REDCap/CSV ingestion, OpenAlex matching, PDF/reference extraction

15

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

pochasset

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): University monorepo package; provenance not yet configured in CI but no other risk signals present.	ai	2026/05/14
bogus-package	bogus-package	AI (bogus-package): Internal university monorepo package; sparse README/keywords are cosmetic, not indicative of spam or malice.	ai	2026/04/29

Versions (showing 15 of 15)

Version	Deps	Published
2.0.2	14 / 8	2026-06-01
1.7.0	14 / 8	2026-04-30
1.6.7	13 / 8	2026-04-29
1.6.6	13 / 8	2026-04-28
1.6.5	13 / 8	2026-04-27
1.6.4	13 / 8	2026-04-27
1.6.3	13 / 8	2026-04-27
1.6.2	13 / 8	2026-04-27
1.6.1	13 / 8	2026-04-10
1.6.0	13 / 8	2026-04-08
1.4.1	11 / 8	2026-04-01
1.4.0	11 / 8	2026-04-01
1.3.0	13 / 8	2026-03-31
1.2.0	13 / 8	2026-03-30
1.1.0	13 / 8	2026-03-27

v2.0.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.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.

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.