← Home

@abp/blogging

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
bogus-package bogus-package AI (bogus-package): ABP framework uses metadata-only npm shims to declare frontend dependencies; tiny payload with link-heavy README is expected for this package family. ai
phantom-deps phantom-dep:@abp/prismjs AI (phantom-deps): No JS code in package; phantom-dep is a false positive for metadata-only shims. ai
phantom-deps phantom-dep:@abp/tui-editor AI (phantom-deps): No JS code in package; phantom-dep is a false positive for metadata-only shims. ai
phantom-deps phantom-dep:@abp/owl.carousel AI (phantom-deps): No JS code in package; phantom-dep is a false positive for metadata-only shims. ai
phantom-deps phantom-dep:@abp/aspnetcore.mvc.ui.theme.shared AI (phantom-deps): No JS code in package; phantom-dep is a false positive for metadata-only shims. ai

Versions (showing 12 of 12)

Version Deps Published
10.4.1 4 / 0
10.4.0 4 / 0
10.3.0 4 / 0
10.2.1 4 / 0
10.2.0 4 / 0
10.1.1 4 / 0
10.1.0 4 / 0
10.0.3 4 / 0
10.0.2 4 / 0
10.0.1 4 / 0
10.0.0 4 / 0
9.3.7 4 / 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. Consider requesting the maintainer enable provenance via CI/CD.

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.