← Home

@abp/timeago

npm Repository Homepage

ABP Framework is a complete open-source infrastructure to create modern web applications by following the best practices and conventions of software development. This package is a part of the [ABP Framework](https://abp.io) and contains client-side files.

12
Versions
LGPL-3.0
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

volohikalkan

Keywords

aspnetcoreboilerplateframeworkwebbest-practicesangularmauiblazormvccsharpwebapp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:timeago AI (dependencies): timeago is a legitimate, well-known npm package; its use here matches the package's stated purpose. ai
bogus-package bogus-package AI (bogus-package): ABP npm packs are intentionally thin wrappers; tiny payload and link-dump README are structural, not spam indicators. ai
phantom-deps phantom-dep:timeago AI (phantom-deps): ABP wrapper packages declare deps for bundling without direct imports; stable pattern across all @abp/* packages. ai
phantom-deps phantom-dep:@abp/jquery AI (phantom-deps): Same ABP wrapper pattern; peer/bundling dependency not directly imported in source. ai

Versions (showing 12 of 12)

Version Deps Published
10.4.1 2 / 0
10.4.0 2 / 0
10.3.0 2 / 0
10.2.1 2 / 0
10.2.0 2 / 0
10.1.1 2 / 0
10.1.0 2 / 0
10.0.3 2 / 0
10.0.2 2 / 0
10.0.1 2 / 0
10.0.0 2 / 0
9.3.7 2 / 0

v10.4.1

1 finding
LOW No provenance attestation provenance

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

v10.4.0

1 finding
LOW No provenance attestation provenance

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

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

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

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

v10.1.1

1 finding
LOW No provenance attestation provenance

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

v10.1.0

1 finding
LOW No provenance attestation provenance

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

v10.0.3

1 finding
LOW No provenance attestation provenance

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

v10.0.2

1 finding
LOW No provenance attestation provenance

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

v10.0.1

1 finding
LOW No provenance attestation provenance

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

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

v9.3.7

1 finding
LOW No provenance attestation provenance

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