← Home

@athenna/core

npm Repository Homepage

One foundation for multiple applications.

36
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jlenon7

Keywords

esmcoreclirestrest-apihttp-serverconsolecroncronjobschedulerignitenodejsathennabootstraptypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped @athenna/core is an established framework package, not a typosquat of cors. ai

Versions (showing 36 of 36)

Version Deps Published
5.42.0 2 / 31
5.41.0 2 / 31
5.34.0 2 / 31
5.33.0 2 / 31
5.32.0 2 / 31
5.31.0 2 / 31
5.30.0 2 / 31
5.29.0 2 / 31
5.28.0 2 / 29
5.27.0 2 / 29
5.26.0 2 / 29
5.25.0 2 / 28
5.24.0 2 / 28
5.23.0 2 / 28
5.22.0 2 / 26
5.21.0 2 / 26
5.20.0 2 / 26
5.19.0 2 / 26
5.18.0 2 / 26
5.16.0 2 / 26
5.15.0 2 / 26
5.14.0 2 / 26
5.13.0 2 / 26
5.12.0 2 / 26
5.11.0 2 / 26
5.10.0 2 / 26
5.9.0 2 / 27
5.8.0 2 / 27
5.7.0 2 / 27
5.6.0 2 / 27
5.5.0 2 / 27
5.4.0 2 / 27
5.3.0 2 / 27
5.2.0 2 / 25
5.1.0 2 / 25
5.0.0 2 / 25

v5.13.0

1 finding
LOW No provenance attestation provenance

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

v5.12.0

1 finding
LOW No provenance attestation provenance

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

v5.11.0

1 finding
LOW No provenance attestation provenance

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

v5.10.0

1 finding
LOW No provenance attestation provenance

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

v5.9.0

1 finding
LOW No provenance attestation provenance

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

v5.8.0

1 finding
LOW No provenance attestation provenance

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

v5.7.0

1 finding
LOW No provenance attestation provenance

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

v5.6.0

1 finding
LOW No provenance attestation provenance

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

v5.5.0

1 finding
LOW No provenance attestation provenance

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

v5.4.0

1 finding
LOW No provenance attestation provenance

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

v5.3.0

1 finding
LOW No provenance attestation provenance

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

v5.2.0

1 finding
LOW No provenance attestation provenance

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

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

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