← Home

@abp/toastr

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.

10
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
publish-pattern dormant-publish AI (publish-pattern): Established ABP framework package with 264 versions; publisher has 21 approved packages and repo matches known abpframework org. ai
dependencies unvetted-dep:toastr AI (dependencies): toastr is a well-known notification library; stable dependency for this package across many versions. ai
bogus-package bogus-package AI (bogus-package): ABP Framework publishes intentionally tiny wrapper packages; link-dump README and small payload are expected for this package family. ai
phantom-deps phantom-dep:toastr AI (phantom-deps): toastr is a peer/bundled dep for ASP.NET Core MVC; not directly imported in JS but re-exported as a bundle dependency. ai
phantom-deps phantom-dep:@abp/jquery AI (phantom-deps): Same-org scoped dep used as a bundle peer; phantom-dep false positive for ABP wrapper packages. ai

Versions (showing 10 of 10)

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.0.3 2 / 0
10.0.2 2 / 0
10.0.1 2 / 0
10.0.0 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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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.